M
Mikko Peltoniemi
I have a Windows 2000 computer that I'm having trouble with the
network shares. I'll call it "computer A". The network also
has other Windows 2000 computers in it, and their shares
work fine. IP addresses are given out with DHCP to all the
computers. All the computers are in the same address block, and
same workgroup.
"Computer A" sees itself and its shares only directly using
its name, or IP address. e.g. \\192.168.0.20. This does
not work from other computers, however.
Network Neighborhood does not work on this computer, but I
can access other computer's shares directly with their IP address,
not their name.
Other computers see "Computer A" in their Network Neighborhood,
but can't connect to it.
When I type "browstat status" on "Computer A" I get
"Browsing is NOT active"
Trying to connect to "Computer A" from another computer
using "net use" I get the following:
"System error 121 has occurred. The semaphore timeout period
has expired."
Everything worked before; has there been maybe a worm
spreading around, or something that could cause this behavior?
Whatever caused this happened some time late last week. The
system logs don't offer any clue.
I can access the internet from "Computer A" without any problems,
so the network itself is OK.
There is no firewall installed on "Computer A", though if a
program blocked connections to port 139/TCP, could the behaviour
be like this?
Details on "Computer A":
W2k SP4, DHCP enabled, Use NetBIOS over TCP/IP enabled, File and
Printer Sharing for Microsoft Networks enabled.
Any help would be great... If not, I guess it's reinstallation
time.
network shares. I'll call it "computer A". The network also
has other Windows 2000 computers in it, and their shares
work fine. IP addresses are given out with DHCP to all the
computers. All the computers are in the same address block, and
same workgroup.
"Computer A" sees itself and its shares only directly using
its name, or IP address. e.g. \\192.168.0.20. This does
not work from other computers, however.
Network Neighborhood does not work on this computer, but I
can access other computer's shares directly with their IP address,
not their name.
Other computers see "Computer A" in their Network Neighborhood,
but can't connect to it.
When I type "browstat status" on "Computer A" I get
"Browsing is NOT active"
Trying to connect to "Computer A" from another computer
using "net use" I get the following:
"System error 121 has occurred. The semaphore timeout period
has expired."
Everything worked before; has there been maybe a worm
spreading around, or something that could cause this behavior?
Whatever caused this happened some time late last week. The
system logs don't offer any clue.
I can access the internet from "Computer A" without any problems,
so the network itself is OK.
There is no firewall installed on "Computer A", though if a
program blocked connections to port 139/TCP, could the behaviour
be like this?
Details on "Computer A":
W2k SP4, DHCP enabled, Use NetBIOS over TCP/IP enabled, File and
Printer Sharing for Microsoft Networks enabled.
Any help would be great... If not, I guess it's reinstallation
time.