Report post You have 30 minutes to complete this form before the CAPTCHA will expire. Security image * Required field JavaScript is required to view this page. Either you do not have JavaScript enabled in your web browser, you do not have cookies enabled in your web browser, or this website is misconfigured such that cookies do not save correctly. This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param="Ubuntu Desktop add to AD Windows Server 2019 problem"]369[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2"><comcode-quote param="Aseroth">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't seem to find any Users (but DHCP, and even the adding of the computer to the AD has no issues).<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]368[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />This sounds like a networking problem. Have you had your networking team take packet captures to see what's going on yet? It sounds like your router isn't set up to route between the different VLANs the way you need it to.<br /><comcode-quote param="Aseroth">Logging in even at the local account returns me back to the login screen.<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]368[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />First, try logging in at a full-screen terminal (Ctrl-Alt-F5) to see if you've broken authentication altogether (which is possible to do when working with PAM.) If you're able to log into the terminal but not a GUI, then the issue is some GUI configuration unrelated to the authentication. For the latter, System76 has a good support article on dealing with that: <a class="user_link" href="https://support.system76.com/articles/login-loop/" rel="nofollow noopener external" target="_blank" title="https://support.system76.com/articles/login-loop/ (this link will open in a new window)">https://support.system76.com/articles/login-loop/</a><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"]369[/post], by jacobgkau [quote="2"] [quote="Aseroth"] 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't seem to find any Users (but DHCP, and even the adding of the computer to the AD has no issues). [snapback]368[/snapback][/quote] This sounds like a networking problem. Have you had your networking team take packet captures to see what's going on yet? It sounds like your router isn't set up to route between the different VLANs the way you need it to. [quote="Aseroth"] Logging in even at the local account returns me back to the login screen. [snapback]368[/snapback][/quote] First, try logging in at a full-screen terminal (Ctrl-Alt-F5) to see if you've broken authentication altogether (which is possible to do when working with PAM.) If you're able to log into the terminal but not a GUI, then the issue is some GUI configuration unrelated to the authentication. For the latter, System76 has a good support article on dealing with that: [url="https://support.system76.com/articles/login-loop/" target="_blank"]https://support.system76.com/articles/login-loop/[/url] [/quote] //// PUT YOUR REPORT BELOW \\\\ Use of this website implies that you agree to the website rules and privacy policy.