NT server XP clients Gateway problems
I have a Vigor 2600 router
A windows NT server
10 Xp xlient machines
THe router is set correctly and the internet is accesble from the server
i set the default gate on the NT server to the same ip address 192.168.0.10 as the router is on.
I get no internet coonection on the xp machines
When i go on to the XP machines and do ipconfig /all all the correct infomation is there correct DHCP server address (address of my server 192.168.0.1) correct subnet mask(255.255.255.0) but the default gate is blank.
i have rebooted the server and work stations to see if this was the problem
I have also deleted leases and renewed the leases.
Next on the Xp machines i manually put in the gateway address and did ipconfig /all and 192.168.0.10 appeared in default gate way hooraahh i hear you say
But still not net access
What my problem
Thanks in advance
Mark
A windows NT server
10 Xp xlient machines
THe router is set correctly and the internet is accesble from the server
i set the default gate on the NT server to the same ip address 192.168.0.10 as the router is on.
I get no internet coonection on the xp machines
When i go on to the XP machines and do ipconfig /all all the correct infomation is there correct DHCP server address (address of my server 192.168.0.1) correct subnet mask(255.255.255.0) but the default gate is blank.
i have rebooted the server and work stations to see if this was the problem
I have also deleted leases and renewed the leases.
Next on the Xp machines i manually put in the gateway address and did ipconfig /all and 192.168.0.10 appeared in default gate way hooraahh i hear you say
But still not net access
What my problem
Thanks in advance
Mark
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Whoa!
"When i go on to the XP machines and do ipconfig /all all the correct infomation is there correct DHCP server address (address of my server 192.168.0.1) correct subnet mask(255.255.255.0) but the default gate is blank."
The default gateway is blank? If so, then that's the problem. You need to set the router option on your DHCP scope and put the address as the internal ip address of your router.
"When i go on to the XP machines and do ipconfig /all all the correct infomation is there correct DHCP server address (address of my server 192.168.0.1) correct subnet mask(255.255.255.0) but the default gate is blank."
The default gateway is blank? If so, then that's the problem. You need to set the router option on your DHCP scope and put the address as the internal ip address of your router.
I have had almost the exact same problem with one of my clients. They had an NT Server (not anymore) and Windows 98, Me, 2000, and XP clients. The 2000 and XP clients frequently would "lose" their default gateway. I came up with a fix that would work.
Assuming that your NT Server has DNS properly configured and you can successfully connect to the Internet from the server, what I did to resolve the problem is specify the SERVER's IP address in the DHCP scope as the default gateway. Once I did that, everyone functioned perfectly.
NT and XP DNS settings don't always mix well. I've had mixed results, but this seemed to permantly fix the problem, until I upgraded them to Windows 2000 Server.
James
Assuming that your NT Server has DNS properly configured and you can successfully connect to the Internet from the server, what I did to resolve the problem is specify the SERVER's IP address in the DHCP scope as the default gateway. Once I did that, everyone functioned perfectly.
NT and XP DNS settings don't always mix well. I've had mixed results, but this seemed to permantly fix the problem, until I upgraded them to Windows 2000 Server.
James
James, You made the NT Server the default gateway? Interesting...did you have to turn on ip forwarding on the NT server? 'Cause I don't see that it would act as a router without that...
So Mark, you have the ip address and subnet mask coming from DHCP, but you've hardcoded the default gateway? (sorry for my earlier braincramp...coffee!!!) I don't have an XP machine on hand, but I'm surprised it lets you do that...did you add the DG to the scope options?
To test out DNS, try visiting a website using it's ip address - if that works, then it definitely is DNS...
try going here and see if it works:
http://129.33.162.37
So Mark, you have the ip address and subnet mask coming from DHCP, but you've hardcoded the default gateway? (sorry for my earlier braincramp...coffee!!!) I don't have an XP machine on hand, but I'm surprised it lets you do that...did you add the DG to the scope options?
To test out DNS, try visiting a website using it's ip address - if that works, then it definitely is DNS...
try going here and see if it works:
http://129.33.162.37
JAmmy.....yes you can hardcode the gateway....of course it would be better if his DHCP was correctly setup....
You can do it in Windows 2000 as well.....try hardcoding only it and then do an IPCONFIG....
When I got to a client I was working on they had 2000 boxes that had DHCP assigned IPs and subnets but to control internet access they only gave the machines they wanted a hardcoded gateway...not very secure LOL....but I guess there users were computer illiterate to know any better.
ASKER
Right i aint at that server today i will look at it tonight and psot the reults up tommorow thanks for the help i reply first thing tommorow.
Mark
Mark
Yeah, I did Jammy. IP forwarding wasn't neccessary. (Don't ask). It just worked. I have used that same fix at multiple sites so it was not just a coincidence. I can't exactly explain it either...
For the record, I've also used the same fix for 98 clients who cannot have multiple gateways but are on a 2000 network. I simply set the 98 clients DG to be the server's IP address, and everything worked perfectly. No IP forwarding was ever configured on the 2K server either.
ASKER
Hello all you all been help full
I add the Router option to scop and Global pointing to 192.168.0.10 to DHCP <--- made no effect
I reset up DNS<---- usinf 192.168.0.1 <---address of server made no effect
I manually put in to each work station the Demon DNS servers Bingo internat works
So the first comment was correct
Thanks for all your help
Mark
I add the Router option to scop and Global pointing to 192.168.0.10 to DHCP <--- made no effect
I reset up DNS<---- usinf 192.168.0.1 <---address of server made no effect
I manually put in to each work station the Demon DNS servers Bingo internat works
So the first comment was correct
Thanks for all your help
Mark
It doesnt sound like you are specifying any servers to perform DNS name resolution.