I am not the normal tech person working with this issue, they are currently off. So I will try to describe this the best I can.
We noticed the last few days that the Computers within the network were no longer connection to our local AD domain, but instead connecting to Network, network1 and so on. Is appears it might be related to a recent windows update, but I am not sure which one, and possibly a settings we have set within the peplink. If we set a computer to a static IP it will connect back with the domain, but we don’t really wish to set every pc to a static IP.
Currently the Peplink handles the DHCP and the windows server is handling DNS and AD domain.
What is the best way to figure out if this is a setting within the peplink keeping the computers from connecting with the domain or a windows setting?
What other information am I missing that would be needed to assist in this?
That’s an interesting fault - seen lots of wierd stuff with recent windows 10 beta tests ( I mean updates) lately.
I can’t immediately imagine how whether the devices IP is statically assigned or dynamically assigned would make much difference - assuming when you statically assign it the configuration is the same?
Might be worth proving that. On a windows PC that is DHCP and not working run ipconfig /all in a command window, do the same on a PC that is statically assigned and copy and paste both results into a notepad window and do a side by side comparison. Would be interesting to see if there are any other differences that just how the address is assigned between a working and non working PC.
I assume there have been no known changes to the Peplink?
You said if you set a static IP you can connect to the domain, but using DHCP you cannot. That makes me wonder if the domain is restricted to a certain IP range or subnet which is different than the domain requires. Look at the IP and subnet that is acquired via DHCP, and compare those numbers to what you set manually. You may need to adjust the DHCP range in the Peplink, or at a minimum set DHCP reservations in the required range for devices that need domain access.
Hello @NetworkNoob,
It is possible that there is a rouge device on your network offering DHCP also. You can operate multiple DHCP servers on one subnet though it is highly discouraged unless you have a very specific user case.
On a PC that is not working correctly & if you know how to get to the Command Prompt, run “ipconfig /all” and note what IPs are getting assigned, check that all the details are what they should being is served correctly from the Peplink (especially the Gateway & DNS that are being assigned).
If your issue is resolved by setting a static IP I suggest you look at what is the gateway you get when receiving IP via DHCP.
Start by pinging the Peplink device, then your AD, verify inter-vlan traffic is enable in the network address your pc’s are getting.
