3 replies
If the IP settings are the same between the workstations with DHCP assigned IP Addresses and those with statically mapped ones, there should be no difference in behavior between them.
The fact only the DHCP machines appear to have a problem indicates a problem with the DHCP scope those machines are leasing an Address from. There is probably a "type-o" or a required IP setting that has been ommited in the scope. The first thing I'd check on the DHCP machines are the IP settings defined in the DHCP scope (IP Address, Default Router, Netmask, etc.). Then compare those settings to one of the statically mapped machines.
To view the TCP/IP configuration on a Win95/98 machine type "WinIPcfg", on a NT/2000 machine go to a "Command Prompt" and type "IPConfig /All". This will display all the settings defined from the DHCP scope that the machine leased the IP Address from. You will probably find something missing on the DHCP machines (Netmask, Default Gateway). Rather than use "telnet", when diagnosing the problem, just "ping" the host(s)-it's simplier. I'd ping local IP Addresses on same subnet as the DHCP clients, and remote subnets on another segment of the router. This should tell you whether it's a "Default Gateway" problem, or a "Netmask" problem.
Hope that helps...
Matt
by kjcc19
by kjcc19
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending