WIN2K Networking Blues

[securit]

Hi, im trying to network 3 win 2k machines through my broadband router, Netgear RO318, I have two of the machines working fully both with the router and file sharing etc. However I have only ust upgraded the last machine and im having problems with it. I can see the machine in my network places yet I can not ping it, I know it is being assignd a DCHP address because it fits in with the other on the standard 192.168.0.x windows settings.

The machine in question can not see me or the other system and when I try to ping any other machines or the router it gives me and error 65 at the cmd prompt, yet I dont know where to find out what this means. It can not access the internet through the router even though its configured in the same way.

I have been having problems with the PCI Simple Communications Device in the Device Manager and this seems to have some kind of error next to it, does this need to be installed or can it just be disabled because as far as im aware it is my modem!?! And my router can also see the machine in its configuration menu.

Many thanks in advance

simon

 

[NickFerrar]

First off check the subnet masks match even if you are sure it got it's IP via DHCP.

Can the PC ping it's loopback address (127.0.0.1) and it's own IP address? That at least tests if the IP stack is loaded properly (or the local routing table isn't hosed).

My guess on error 65 would be a firewall blocking ICMP (ping), do you have firewall software on the troublesome PC? If not have you checked the config on the router?

 

[securit]

Yes the PC can ping its own address @ 127.0.0.1 with no problems, when the subnet masks are assigned by dchp the masks are automatically assigned along with the ip address and ive checked its the same.

I think the problem has something to do with the Simple Communications Device and im not sure what to install this as.

 

[Alshrim]

how are you pinging the device??

ping computername?
or
ping 192.168.x.x ?


if it doesn't resolve with "ping computername" then you have a dns issue... or the Workgroup name isn't properly specified...

and ya.. if the drivers aren't correct.. that will cause a problem with tcp/ip binding... 3com NIC's don't always install by default, for example ... you'd have to install the drivers manually. I think the first thing I would do is update the NIC drivers... see what that fosters ... look at workgroup settings ... just to rule it out ... reinstall Tcp/ip of both those other things are ok .. just to rule out a corrupted TCP/IP Stack ...

IF none of that works... we've ruled out the common things .. and we can think on some other less common things.
Alshrim
System Administrator
MCSE, MCP+Internet

 

[DeadEye]

Hi Securit,

Did you configure the Netgear box for DHCP ?

If you go to each system do they all have IP addresses in the range that your router is handing out, netmask and default router, DNS etc...
One nasty things about Win2K is it's automatic IP addressing ability.
If it is configured for DHCP and it doesn't get one ( in time ? ) it will give itself an address in the range 169.254.x.x

see -

http://support.microsoft.com/default.aspx?scid=kb;en-us;244268

http://support.microsoft.com/default.aspx?scid=kb;en-us;260888

 

[securit]

Hi everyone,

Im trying to ping the IP address and so I can reasonably assume that its not a DNS problem.

Deadeye, already been through that problem with one of the otehr machines, sorted it out and for this machine dhcp is working correctly. I did have some teething problems with it but its ok now.

The Simnple Communications Device I think is the problem, I can not think of what to install this as, is it my modem or is it the Network Card? The card appears to have installed correctly and all the diag looks ok, the modem is not installed at the moment which makes me think that this is the problem.

Could removing the modem card sort this problem out? I have already re-installed all the IP protocols etc and am running out of ideas fast!

thanks for all the replies