PUZZLED: 2 systems cannot connect but all others do

[John7]

Hi,



I am totally puzzled about this problem.

For a while, with no apparant reason, one PC (#A) can no longer connect
to my file server (#F, Windows 2000 pro) while other PC's (#B,#C,...) can.

I found:
A pings B: OK
A pings F: ***FAIL***
---------------
B pings A: OK
B pings F: OK
---------------
F pings A: ***FAIL***
F pings B: OK

So: A <--> F do not connect, all others connect fine.

All PC's run WinXP pro, fully updated.
No firewalls enabled.
Default Gataway (router) has DHCP enabled., no other DHCP's.
DHCP-range and fixed IP's are not overlapping.
All systems:
- have unique fixed IP-adresses in subnet 192.168.2.xxx
- have NetBios manually enabled (because of fixed IP).
- have Default Gateway set to 192.168.2.1
- have DNS1 set to 192.168.2.1
- can access internet (and email).
Cables seem fine.

I ran through KB314067 but found no clues.

I cleared the ARP-cache on PC #A and file server #F but to no avail.
At PC #A I added a static entry using file server #F MAC address and it's
fixed IP.
Even then I was not able to ping A --> F and F --> A.


Any clues ?


Remaining puzzled.....
John7

 

[Mark L. Ferguson]

Compare all user names on A with the machine name of F, and also all user
names on F with the machine name of A. You could find a collision.

 

[EM]

You might try reinstalling your network drivers on #A,SFC, or a system repair/reinstall
A Little Bit of Everything..
http://www.whaatsoever.com

 

[John7]

Hello Mark,

Thanks for responding.
Point is even below account checks the network isn't functioning.
It won't come to this point.
I simply cannot ping computers A <--> F.
All others ping fine.

John7

 

[John7]

Hi,


I reinstalled the network card driver but to no avail.
A complete reinstall is no option.

John7
"EM" <[email protected]> schreef in bericht You might try reinstalling your network drivers on #A,SFC, or a system repair/reinstall
A Little Bit of Everything..
http://www.whaatsoever.com

 

[Guest]

Sounds like a subnet mask issue... I would do a gut check on the subnet
mask... perhaps someone fat fingered the subnet mask