E
Evan Ruff
Hello,
I have a network of three Windows XP Pro machines. All machines are in
the same workgroup, with no firewalls enabled and no weird
configurations. Two of the computers network fine, able to access all
shares/browse/etc.
The thrid computer is really giving me fits. I can't access any other
shares or browse the workgroup (it doesn't list anything) I can't
access the other computers, either by \\hostname or by \\IP address.
NetBIOS over TCP/IP is enabled on all computers. Ping works. Browstat
status returns nothing at all (just a blank line).
I have reset all the local security settings with no effect.
When I go to access one of the other computers, it just says "The
network location cannot be reached. For more information about Network
Troubleshooting, see Windows Help." This happens if I attempt to
browse to the computer either by hostname or IP. I can ping the IP
without issues.
I would really appreciate it if you guys could help me trouble shoot
this issue. I think something is going on that's beyond my knowledge
of the Windows networking stack.
Thanks a lot!
Evan Ruff
I have a network of three Windows XP Pro machines. All machines are in
the same workgroup, with no firewalls enabled and no weird
configurations. Two of the computers network fine, able to access all
shares/browse/etc.
The thrid computer is really giving me fits. I can't access any other
shares or browse the workgroup (it doesn't list anything) I can't
access the other computers, either by \\hostname or by \\IP address.
NetBIOS over TCP/IP is enabled on all computers. Ping works. Browstat
status returns nothing at all (just a blank line).
I have reset all the local security settings with no effect.
When I go to access one of the other computers, it just says "The
network location cannot be reached. For more information about Network
Troubleshooting, see Windows Help." This happens if I attempt to
browse to the computer either by hostname or IP. I can ping the IP
without issues.
I would really appreciate it if you guys could help me trouble shoot
this issue. I think something is going on that's beyond my knowledge
of the Windows networking stack.
Thanks a lot!
Evan Ruff