WinXP Pro & Win2K Pro Network - Help, or the computer gets it

[Traveler]

Sorry for the long post, but...

I have a small network problem that is pissing me off. I have recently
added a win2k computer to an existing workgroup network, and cannot
access shares from or to this machine, or even see other computers on
the network.

There are seven other computers on this network, winxp pro and win2k
pro. I have one router and a slew of switches, wall jacks and hubs
(there are other nodes besides computers). I verified the network
cable/physical layout with an xp machine, and the cable/network works
fine. I transferred the cable to the new 2k machine, and here's what's
threatening the health of others...

The router broadcasts DHCP and the win2k is set up as a client. It
obtains an IP successfully, and I am able to ping the gateway and other
machines on the network (by ip only - no netbios) I am able to ping
foreign ips (internet) and domain names (DNS resolves, obviously).
NetBIOS over TCP/IP is enabled, no firewalls for any machines (hardware
between router and modem). When I use the 'net view' command, I can see
the new machine, but if I try 'net view NAME', I get a network path not
found error. From any other machine I can see the new computer, but if
I try to access it, I get a '\\NAME is not accessible' error. I cannot
even see the network with the new machine at all. I tried flushing the
net config scripts (since it was factory installed) and that didn't
help.

Now to add some more weirdness. The new win2k machine is running an
Apache web server for file access (factory installed - this machine is
connected to a large format scanner) and I am able to access the web
server from any other machine. I also cannot access any web site with
the new machine - local network or internet (except itself through
loopback).

I also have printers on this network that are equipped with onboard
ethernet cards, so I add them as 'local printer/new tcp-ip port...' and
I can add a printer on the new machine this way and print to it.

All I want to do is share files, any help would be appreciated. I know
it has to be something stupid, but I'm ready to rm -rf the ****ing
thing.

Thanks.

 

[Hans-Georg Michna]

I have recently
added a win2k computer to an existing workgroup network, and cannot
access shares from or to this machine, or even see other computers on
the network.
'\\NAME is not accessible' error

Traveler,

check http://winhlp.com/wxnet.htm .

Hans-Georg

 

[Chuck]

Sorry for the long post, but...

I have a small network problem that is pissing me off. I have recently
added a win2k computer to an existing workgroup network, and cannot
access shares from or to this machine, or even see other computers on
the network.

There are seven other computers on this network, winxp pro and win2k
pro. I have one router and a slew of switches, wall jacks and hubs
(there are other nodes besides computers). I verified the network
cable/physical layout with an xp machine, and the cable/network works
fine. I transferred the cable to the new 2k machine, and here's what's
threatening the health of others...

The router broadcasts DHCP and the win2k is set up as a client. It
obtains an IP successfully, and I am able to ping the gateway and other
machines on the network (by ip only - no netbios) I am able to ping
foreign ips (internet) and domain names (DNS resolves, obviously).
NetBIOS over TCP/IP is enabled, no firewalls for any machines (hardware
between router and modem). When I use the 'net view' command, I can see
the new machine, but if I try 'net view NAME', I get a network path not
found error. From any other machine I can see the new computer, but if
I try to access it, I get a '\\NAME is not accessible' error. I cannot
even see the network with the new machine at all. I tried flushing the
net config scripts (since it was factory installed) and that didn't
help.

Now to add some more weirdness. The new win2k machine is running an
Apache web server for file access (factory installed - this machine is
connected to a large format scanner) and I am able to access the web
server from any other machine. I also cannot access any web site with
the new machine - local network or internet (except itself through
loopback).

I also have printers on this network that are equipped with onboard
ethernet cards, so I add them as 'local printer/new tcp-ip port...' and
I can add a printer on the new machine this way and print to it.

All I want to do is share files, any help would be appreciated. I know
it has to be something stupid, but I'm ready to rm -rf the ****ing
thing.

Thanks.

Calm down and step away from the defenseless computer. ;-)

The '\\NAME is not accessible' error could have several causes. Firewalls
(maybe one associated with your antivirus?) are one, very common, possibility,
but there are others.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html

Let's start by looking at "browstat status" and "ipconfig /all" from the problem
computer, and from 2 properly working computers. With all 6 diagnostics, we
should be able to narrow down the problem. Steps 3 and 4, in this article,
should get you started.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html