You have 30 minutes to complete this form before the CAPTCHA will expire.

Security image * Required field
This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param=&quot;Ubuntu Desktop add to AD Windows Server 2019 problem&quot;]368[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by Aseroth<br /><br /><comcode-quote param="252">I am actually a noob when it comes to ubuntu, let alone linux….<br />The network infrastructure demands that devices needs to be separated by VLAN. All of them are done without any issues so far. Everything works as intended except for this one.<br /><br />The windows server serves as both the domain controller and DHCP for almost the entirety of the network. Connecting clients with Windows 10 works fine in any of the VLANs within the network, both the DHCP and Active Directory (login) works just fine. However when it comes to the Ubuntu, only the ones connected in the same VLAN (subnet) of the said server works, once it goes to a different VLAN, regardles of when the configuration is done. It can&#39;t seem to find any users but manages to get an IP from the DHCP and even find the kinit and even add itself to the Windows Server Active Directory Computer. I followed the turtorial here: <a class="user_link" href="https://nerdonthestreet.com/wiki?find=Authenticate+Ubuntu+19.04+against+Active+Directory" rel="nofollow noopener" target="_top">https://nerdonthestreet.com/wiki?find=Authenticate+Ubuntu+19.04+against+Active+Directory</a> and it seems to work perfectly when both of my ubuntu client and Windows server are on the same VLAN (subnet) and as I mentioned earlier, when it goes to a different VLAN or if it was created on a different VLAN, it can&#39;t seem to find any Users (but DHCP, and even the adding of the computer to the AD has no issues).<br /><br />It is imperative that the clients belong to it&#39;s own VLAN but using Windows is not feasible. Please advise.<br />Thank you so much!<br /><br />Regards,<br />Aseroth<br /><br />PS: When I try to transfer the said instance/unit to the same vlan as the server, it works just fine. I tried creating a VLAN for interface (NIC Teaming) of the Windows Server, creating subnets for SItes and Services but to no avail. Windows Clients work just fine to the ports/vlans where the ubuntu will fail to work. Again hoping to hear from you guys! thank you!<br /><br />PPS: I think I managed to see the users now by changing the address of the one in the /etc/hosts of the Server to the one that I created in the NIC Teaming which belongs to the same subnet, and was able to &quot;login&quot; to the accounts on the users of the AD, however with that, I am now stuck in a login loop. Logging in even at the local account returns me back to the login screen. Thanks again.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color [Font] Arial Courier Georgia Impact Times Trebuchet Verdana Tahoma Geneva Helvetica [Size] 0.8 1 1.5 2 2.5 3 4 [Color] Black Blue Gray Green Orange Purple Red White Yellow This is a reported post for a post in the topic [post param="Ubuntu Desktop add to AD Windows Server 2019 problem"]368[/post], by Aseroth [quote="252"] I am actually a noob when it comes to ubuntu, let alone linux…. The network infrastructure demands that devices needs to be separated by VLAN. All of them are done without any issues so far. Everything works as intended except for this one. The windows server serves as both the domain controller and DHCP for almost the entirety of the network. Connecting clients with Windows 10 works fine in any of the VLANs within the network, both the DHCP and Active Directory (login) works just fine. However when it comes to the Ubuntu, only the ones connected in the same VLAN (subnet) of the said server works, once it goes to a different VLAN, regardles of when the configuration is done. It can&#39;t seem to find any users but manages to get an IP from the DHCP and even find the kinit and even add itself to the Windows Server Active Directory Computer. I followed the turtorial here: [url="{$BASE_URL*}/wiki?find=Authenticate+Ubuntu+19.04+against+Active+Directory" rel="nofollow noopener nofollow noopener nofollow noopener nofollow noopener nofollow noopener nofollow noopener nofollow noopener" target="_top"]https://nerdonthestreet.com/wiki?find=Authenticate+Ubuntu+19.04+against+Active+Directory[/url] and it seems to work perfectly when both of my ubuntu client and Windows server are on the same VLAN (subnet) and as I mentioned earlier, when it goes to a different VLAN or if it was created on a different VLAN, it can&#39;t seem to find any Users (but DHCP, and even the adding of the computer to the AD has no issues). It is imperative that the clients belong to it&#39;s own VLAN but using Windows is not feasible. Please advise. Thank you so much! Regards, Aseroth PS: When I try to transfer the said instance/unit to the same vlan as the server, it works just fine. I tried creating a VLAN for interface (NIC Teaming) of the Windows Server, creating subnets for SItes and Services but to no avail. Windows Clients work just fine to the ports/vlans where the ubuntu will fail to work. Again hoping to hear from you guys! thank you! PPS: I think I managed to see the users now by changing the address of the one in the /etc/hosts of the Server to the one that I created in the NIC Teaming which belongs to the same subnet, and was able to &quot;login&quot; to the accounts on the users of the AD, however with that, I am now stuck in a login loop. Logging in even at the local account returns me back to the login screen. Thanks again. [/quote] //// PUT YOUR REPORT BELOW \\\\ Use of this website implies that you agree to the website rules and privacy policy.