We have a Windows 2003 domain with clients using DHCP and have plenty of free addresses available, but there has been one machine that gets assigned to "Network 2" instead of our domain, and it gets an IP address of 192.168.0.255. It then cannot access the internet but can reach some resources on the network (it can ping the gateway of 192.168.1.1 and the IP of the DNS server, but not the DNS server by name). If we give it a static IP address and manually assign network settings, it connects just fine. We've tried running netsh winsock, tried resetting TCP/IP, uninstalled and reinstalled the network adapter drivers, etc, but nothing seems to fix this issue. The issue wouldn't normally be a big deal but we've had one or two other machines that have had that same issue at different times; we've assigned those machines to static addresses just to temporarily solve the problem. DHCP server is running fine with no errors and other machines are getting correct leases, so we don't think that is the issue, but we are running out of ideas...anyone seen this issue before? Thanks for any ideas you can offer in advance....
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Certain clients on Windows 2003 domain get assigned to Network 2, IP address of 192.168.0.255?
- Thread starter mdcr1
- Start date
VinceWhirlwind
Technical User
If you disable your DHCP scope and reboot this machine, does it still get this undesirable address?
It might help if you gave more precise details, eg, "our PCs are on the 192.168.1.0/24 subnet". "We use a single VLAN on all our switches". Or not, as the case might be.
It might help if you gave more precise details, eg, "our PCs are on the 192.168.1.0/24 subnet". "We use a single VLAN on all our switches". Or not, as the case might be.
- Thread starter
- #3
We've disabled the DHCP service and rebooted the machine, and then it gets the self assigned address of 169.254.x.x (as if it's disconnected from all networks). Our subnet is 255.255.254.0, so the range of all of our devices (PCs, IP phones, and about 8 printers) is 192.168.0.1 to 192.168.1.254.
- Thread starter
- #4
We've excluded 192.168.0.255 from the range of addresses, because .0.255 was actually being assigned (when we checked the DHCP leases), but should it have been assigned? It seems like that is an invalid address and just because it was/is in the range doesn't mean it should be assigned... after releasing and renewing the adapter for that computer, it comes up fine, does that make sense?
VinceWhirlwind
Technical User
You say you're using the subnet mask of 255.255.254.0.
Presumably, your network address is 192.168.0.0
192.168.0.255/23 is a valid host address.
The issue is probably with the machines that were not communicating with it. Their subnet mask is wrong, perhaps, or they have a crappy IP stack.
Some older devices won't even do 192.168.0 anything. Others might assume evrything is a /24 and have trouble with 0.255 as a result.
If the servers are on a different subnet, then your router/gateway is probably the problem.
Presumably, your network address is 192.168.0.0
192.168.0.255/23 is a valid host address.
The issue is probably with the machines that were not communicating with it. Their subnet mask is wrong, perhaps, or they have a crappy IP stack.
Some older devices won't even do 192.168.0 anything. Others might assume evrything is a /24 and have trouble with 0.255 as a result.
If the servers are on a different subnet, then your router/gateway is probably the problem.
- Status
Similar threads
- Locked
- Question