Default Gateway Sometimes Not Right

[augrunt]

Hello Everyone, I am pretty much a "noob" to the whole DHCP/DNS concept on a Windows Server machine but I am eager to learn and have fixed a few issues in regards to what has been setup in the organization...

However, there is this one issue I can't seem to narrow down and weed out and it is that sometimes, when a user restarts their computer and there I.P. is reassigned it is given the wrong "Default Gateway" (192.168.0.101, the server itself), If I try releasing and renewing on the client PC, it does nothing. But the second I disable his/her adapter and re-enable it, it is assigned the proper one. Where in the world is it getting the wrong Default Gateway from?

Here is how the Network is setup

Router/Internet: 192.168.0.1 [Correct Gateway]
Domain Controller: 192.168.0.101
Domain Controller 2: 192.168.0.102

What settings Do I need to look at? Why does it fix itself once I disable/re-enable the adapter?

Thanks! Hope you guys can help!

 

[58sniper]

First thing I'd look for is another DHCP server somewhere, that's giving out the wrong info.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[augrunt]

I looked at the router... DHCP disabled
I looked at the 192.168.0.101 server, it's ROUTER is pointing to 192.168.0.1

the only thing is 192.168.0.102 -- the 2nd domain controller, but the DHCP on that isnt enabled.

Heres another relevant issue, if i connect via the VPN the IP address it assigns me (for example 192.168.0.93) I am given the exact same address as my gateway (I dont know if that is normal or what, but I know checking "Do not use remote default gateway" fixes it.

 

[58sniper]

Verify you have a single scope configured. Next time it happens, do an ipconfig /all on that "problem" workstation and verify the DHCP is what it should be.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Roadki11]

ipconfig /all will also tell you the dhcp server that issued the lease, that should lead you to the misconfigured scope or rogue server.


RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen

 

[augrunt]

Hey guys,

I see a possible issue here... I just noticed that when it is .101 it has an extra domain listed under DNS Suffix Search List called "mshome.net"

[Problematic Gateway Screenshot]


[Correct Gateway Screenshot]

 

[augrunt]

Hey guys,

I see a possible issue here... I just noticed that when it is .101 it has an extra domain listed under DNS Suffix Search List called "mshome.net"

[Correct Gateway Screenshot]


[Problematic Gateway Screenshot]

 

[augrunt]

Oh come on! I tried editing it and it posted 2 threads! okay guys the 2nd one with the screenshots is the correct labelling. "mshome.net" is what is appearing in the problematic screenshot.

Where in the world did mshome.net come from?

 

[augrunt]

Another note:

On the problematic IPCONFIG
the Node type is set to "mixed"

However, on the correct side of things
it's set as "Hybrid"

and according to information from another forum
1. hybrid-----> querries wins first and then it querries dns
2. mixed------> querries dns first and then wins

What do I do from here guys?