dankyle67
asked on
Internet connections get disconnected incoming and outgoing
DHCP server shows up internal ip address as 169.x.x.x which seems incorrect since it should show up as internal 10.x.x.x for nic card on server. I tried resolving the secondary dns server under scope options and it resolved it as correct 10.x.x.x but the primary dns was resolving to the 169.x.x.x address. Does this sound right? We have been having disconnects in the office to the internet as wells as remote users logging into the remote desktop server getting disconnected so we are not sure at this point if there is any correlation between the dhcp/dns issues and the internet disconnects. I would think if users get kicked out of internet sessions both going out and coming in then it might be the router. Any ideas? thanks
John
The 169 Address is an internal address because Address from the DHCP Server is not available. Where does the DHCP Server get it’s Address and is it running out of Address space
ASKER
The 169 address is showing up when i go to the dhcp server settings. The dhcp ip leases are good for 200 addresses and we only have 10 pcs in the office so it should not have run out of ip leases. Should i do anything so that the ip address that shows up on the dhcp server becomes 10.10.x.x instead of the 169.x.x.x?
Can you restart the DHCP Server?
One Workstation or more than one having the issue?
One Workstation or more than one having the issue?
Also internally use IPv4 Addresses . Do not disable IPv6 but make sure the DHCP Server is handing out IPv4 addresses internally
ASKER
How do i restart the dhcp server? I have not disabled ipv6 but what i was trying to point out was that when i got to the dhcp settings the address on the very top level shows up as 169.x.x.x so are you saying this is incorrect?
ASKER
There is an option to deauthorize dhcp server so should i do that or should i just stop and start the dhcp service under services
What is your DHCP Server? Router or Server like Server 2012?
If a server, close all and restart the server.
If router remove AC power , wait for 15 seconds and plug back in
If a server, close all and restart the server.
If router remove AC power , wait for 15 seconds and plug back in
ASKER
Our dhcp server is a 2012 server so i restarted the dhcp server but it still shows up as 169.x.x.x i really dont wanna restart server if possible but if i have to then i will. Someone suggested that we use the router to handle the dhcp leases. Do you recommend this and how do you go about doing that, We have a cradlepoint router.
You can also try restarting the services. Do not disable.
Make certain the router has DHCP Server disable that on the router.
Make certain the router has DHCP Server disable that on the router.
Make sure as stated above that the router has DHCP disabled
As a test turn off the router, restart the server, and see if internally the Workstations get good Addresses
ASKER
I agree with all you stated so far about making sure that dhcp is disabled on cradlepoint router so as not to conflict with 2012 dhcp server currently on the network but problem is that the owner of the company decided last year to set this up all on his own without letting me know the username and password to access the router so i cant even check if dhcp is enabled on it and can't restart it so i will have to ask him to restart it tomorrow and to check if dhcp is enabled on it. So are you saying that on the dhcp server running on the 2012 server it should come up as an internal ip address instead of the 169.x.x.x?
the server that is hosting dhcp must have a static ip address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry only got reply back now from the person who called up the cradlepoint router support and they said they didnt see any issues as far as internet connections getting dropped and they confirmed that dhcp is disabled. The strange thing is everytime they restart the dhcp server on the network then everything works including external remote desktop sessions trying to log into the dedicated remote desktop server. Why would they even be affected since the server they are logging into has a static ip address. Let's assume we turned off the dhcp server. Then external users tried logging in thru remote desktop to the other remote desktop server. Shouldnt they be able to access that server without having any reliance on the dhcp server? Unless they require the dhcp server to be up and running since it is also the main domain controller which means if it is down or now working properly then domain user authentication could cause them to be kicked off and not necessarily losing internet connection but losing domain access. I have noticed some kerberos errors referencing that global policies are not getting replicated so wonder if this might be the actual issue. I guess a way to test this is if someone gets disconnected from internet they could hardcode ip address and ip info so that they are not relying on dhcp then if they still cant get to internet then it could possibly be that they are getting disconncted from domain and not the internet. Does this make sense?
Make sure people are using DHCP and not static IP addresses. That can cause a conflict. Make sure there is only one DHCP Server anywhere in your shop
ASKER
They are all using dhcp and there is only one dhcp server. As i mentioned, when they restarted it both times the users were able to all get back on the internet outgoing and also incoming via remote desktop sessions.
Maybe do a Repair Install on your Server to fix this
ASKER
The dhcp server has been working for past few days so I think users were just getting disconnected when the service was not running. Thanks for the help
You are very welcome and thanks for the update.