Win2K shares not visible from one XP Pro machine

G

Guest

I've got a network with a Win2K Workstation serving a small Access database
from a share called "database". There is another Win2K machine and two WinXP
Pro machines that can access this computer by name or IP correctly. However,
I have a WinXP Pro machine that cannot view the shares by either IP or name.
It cannot even view its own shares by IP (works by name). The WinXP system
can ping any system on the network by name or IP. Doing "net view \\ip" of
the local machine does not work, but doing "net view \\name" does work.
Doing a "net view" of any other machine by name or IP fails with "System
Error 53". All machines have unique names and are in the same workgroup.
There is no domain present. IP addresses are assigned by DHCP from the
router. Guest account is enabled on the Win2K system housing the share and
the other 3 machines can connect just fine. because of the problem using
"net view \\name" for the local machine, I suspect the issue is with this
machine. I have tested with the WinXP firewall on and off, disabled
SpySweeper that is installed and disabled Symantec Anti-virus corporate to
test. None of these things have any effect.
 
C

Chuck

I've got a network with a Win2K Workstation serving a small Access database
from a share called "database". There is another Win2K machine and two WinXP
Pro machines that can access this computer by name or IP correctly. However,
I have a WinXP Pro machine that cannot view the shares by either IP or name.
It cannot even view its own shares by IP (works by name). The WinXP system
can ping any system on the network by name or IP. Doing "net view \\ip" of
the local machine does not work, but doing "net view \\name" does work.
Doing a "net view" of any other machine by name or IP fails with "System
Error 53". All machines have unique names and are in the same workgroup.
There is no domain present. IP addresses are assigned by DHCP from the
router. Guest account is enabled on the Win2K system housing the share and
the other 3 machines can connect just fine. because of the problem using
"net view \\name" for the local machine, I suspect the issue is with this
machine. I have tested with the WinXP firewall on and off, disabled
SpySweeper that is installed and disabled Symantec Anti-virus corporate to
test. None of these things have any effect.
Click to expand...

You're on the right track. One of the most common causes of this problem would
be a misconfigured or overlooked personal firewall, or other security component.
Symantec products may contain an antiworm protection, that also can act as a
firewall and block traffic. There are other possibilities too.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
 
G

Guest

Checked that, hence the reason I said I disabled the anti-virus and
anti-spyware software. I also notice that your response to me is the same as
numerous other you have posted in this forum. Did you read my original post
or stop after I said one machine couldn't see another? I don't mean to be
offensive and I'm sorry if it comes out that way, but after spending over 5
hours dealng with this problem so far and searching these groups and much of
the internet to no avail, rehashing what I have read and tried isn't fixing
my problem. Any other suggestions?
 
G

Guest

Try 2 things

Check "File and Print sharing for microsoft Networks " on LAN card

Second in Windows explorer -->tools--> view-->Use Simple file sharing
(Recommended) . Uncheck this

do update if that resolved or still problem exists
 
G

Guest

"File and Print sharing" is on for both computers. "Simple File Sharing" is
disabled where applicable (no such setting for Win2K).
 
C

Chuck

Checked that, hence the reason I said I disabled the anti-virus and
anti-spyware software. I also notice that your response to me is the same as
numerous other you have posted in this forum. Did you read my original post
or stop after I said one machine couldn't see another? I don't mean to be
offensive and I'm sorry if it comes out that way, but after spending over 5
hours dealng with this problem so far and searching these groups and much of
the internet to no avail, rehashing what I have read and tried isn't fixing
my problem. Any other suggestions?
Click to expand...

You noted having disabled Symantec. If you spend some time reading other
threads, you'll note that:
1) Symantec products don't always disable politely.
2) Some Symantec products contain other components, like antiworm protection,
which will act as a firewall, and block SMBs. Antiworm protection won't disable
with the firewall off switch.

When you talk about computers that can't see one another, you're talking about
blocked browser SMBs.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

So you referred to having turned off the personal firewall (which may or may not
do anything). My article talks about a lot more than that, including
diagnostics that you can do on your own, or with help here.

If it offends you that I provide the same starting advice in a number of posts,
I apologise. But my initially cited article is relevant to your problem, and
I'll bet there are a few items in there that you haven't tried.

You can start with "error = 53", if you like.
<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
 
G

Guest

Well Chuck, after reading through all of the links you sent and trying
anything that even could have been relevant to my problem, the computer still
cannot see any other computer connected to the same network it's on. I also
notice that cdiag seems to be nothing more than a batch script with comments
detailing the steps I've already taken and putting it all into a texzt
document. Also, since this is a corporate computer that I did not load and I
was unsure if it had been cloned from an image, I even went as far as to
change the SID with Mark R's NewSID tool from MS site. This had no effect.
Someone also suggested that I turn off Simple File Sharing on the XP machine
that is having problems seeing shares on the 2000 machine. not sure why it'd
have an effect, but it is now off as well. I am considering reloading the
system to see if that will resolve my issues (as reloading Windows does tend
to fix many problems unfortunately). The number of installed pieces of
software on the system is minimal consisting of basic office applications,
Symantec 10.0.0 Corporate and SpySweeper 5.2.3.

How exactly does Windows determine that a name isn't found when it can ping
the name of the machine? Or how does Windows determine that a name can't be
found when you give the IP to connect to instead?

These commands provide these results: (192.168.1.2 [dh16mm51] remote 2K
system with share, 192.168.1.4 [optiplex320] is local system with some shared
printers)
ping 192.168.1.2
Click to expand...
Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
ping dh16mm51
Click to expand...
Pinging dh16mm51 [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
net view \\192.168.1.4
Click to expand...
System error 51 has occurred.

Windows cannot find the network path. Verify that the network path is
correct and the destination computer is not busy or turned off. If Windows
still cannot find the network path, contact your network administrator.
net view \\optiplex320
Click to expand...
Shared resources at \\optiplex320

MEREDITH

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
Printer2 Print Adobe PDF
Printer3 Print Xerox WC M20 Series PCL 6
Printer5 Print Dell Laser Printer 1700n
SharedDocs Disk
The command completed successfully.
net view \\192.168.1.2
Click to expand...
System error 53 has occurred.

The network path was not found.
net view \\dh16mm51
Click to expand...
System error 53 has occurred.

The network path was not found.
ipconfig /all
Click to expand...
Windows IP Configuration

Host Name . . . . . . . . . . . . : optiplex320
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controller
Physical Address. . . . . . . . . : 00-13-72-39-14-6F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Monday, May 07, 2007 2:37:28 PM
Lease Expires . . . . . . . . . . : Monday, May 07, 2007 3:37:28 PM
net config server
Click to expand...
Server Name \\OPTIPLEX320
Server Comment MEREDITH

Software version Windows 2002
Server is active on
NwlnkIpx (000000000001)
Nbf_NdisWanNbfOut{E57CF9F4-9AEA-4EFC-99D1-C4C1D633B8BF} (2ade20524153)
Nbf_NdisWanNbfOut{22BB62AD-7B9A-4865-8E52-997DA6AB16EE} (2ade20524153)
Nbf_NdisWanNbfIn{0E8257D2-0653-4C6E-B875-31BD88F2062E} (2ade20524153)
NetbiosSmb (000000000000)
Nbf_NdisWanNbfOut{3439A0D7-D43E-49BA-B85C-425CF0C09F5E} (2ade20524153)
Nbf_NdisWanNbfIn{8FC99D47-DBB0-4C5C-8E06-F03E191AE3C8} (2ade20524153)
Nbf_NdisWanNbfIn{E29424C1-CF03-4A8C-8136-14CE96565834} (2ade20524153)


Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.
net config workstation
Click to expand...
Computer name \\OPTIPLEX320
Full Computer name optiplex320
User name VPSI Houston

Workstation active on
Nbf_NdisWanNbfOut{22BB62AD-7B9A-4865-8E52-997DA6AB16EE} (2ADE20524153)
Nbf_NdisWanNbfIn{0E8257D2-0653-4C6E-B875-31BD88F2062E} (2ADE20524153)
Nbf_NdisWanNbfIn{E29424C1-CF03-4A8C-8136-14CE96565834} (2ADE20524153)
Nbf_NdisWanNbfIn{8FC99D47-DBB0-4C5C-8E06-F03E191AE3C8} (2ADE20524153)
Nbf_NdisWanNbfOut{3439A0D7-D43E-49BA-B85C-425CF0C09F5E} (2ADE20524153)
Nbf_NdisWanNbfOut{E57CF9F4-9AEA-4EFC-99D1-C4C1D633B8BF} (2ADE20524153)
NetbiosSmb (000000000000)

Software version Windows 2002

Workstation domain VPSI
Workstation Domain DNS Name (null)
Logon domain OPTIPLEX320

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.
browstat status
Click to expand...
Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfIn{0E8257D2-0653-4C6E-B875-31BD88F2062E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfOut{E57CF9F4-9AEA-4EFC-99D1-C4C1D633B8BF}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfOut{3439A0D7-D43E-49BA-B85C-425CF0C09F5E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfOut{22BB62AD-7B9A-4865-8E52-997DA6AB16EE}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfIn{8FC99D47-DBB0-4C5C-8E06-F03E191AE3C8}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfIn{E29424C1-CF03-4A8C-8136-14CE96565834}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Is there any other information that is needed?
 
C

Chuck

Well Chuck, after reading through all of the links you sent and trying
anything that even could have been relevant to my problem, the computer still
cannot see any other computer connected to the same network it's on. I also
notice that cdiag seems to be nothing more than a batch script with comments
detailing the steps I've already taken and putting it all into a texzt
document. Also, since this is a corporate computer that I did not load and I
was unsure if it had been cloned from an image, I even went as far as to
change the SID with Mark R's NewSID tool from MS site. This had no effect.
Someone also suggested that I turn off Simple File Sharing on the XP machine
that is having problems seeing shares on the 2000 machine. not sure why it'd
have an effect, but it is now off as well. I am considering reloading the
system to see if that will resolve my issues (as reloading Windows does tend
to fix many problems unfortunately). The number of installed pieces of
software on the system is minimal consisting of basic office applications,
Symantec 10.0.0 Corporate and SpySweeper 5.2.3.

How exactly does Windows determine that a name isn't found when it can ping
the name of the machine? Or how does Windows determine that a name can't be
found when you give the IP to connect to instead?

These commands provide these results: (192.168.1.2 [dh16mm51] remote 2K
system with share, 192.168.1.4 [optiplex320] is local system with some shared
printers)
Click to expand...

Ben,

Name resolution on small LANs uses NetBIOS Over TCP broadcasts (sent to
192.168.1.255). It's possible that a computer could respond to a name
resolution broadcast, and provide its IP address in response, yet not respond to
an individually directed IP transaction (ICMP Echo for instance).

An error = 51 is "path not found", which specifically refers to the IP address,
NOT to the computer name.

One of the reasons for CDiag is to provide all of the tests (as you noted), but
provide them canonically, and religiously in order, and well labeled. The tests
that you provide below are neither. When you're looking at a 2 way, or 3 way,
test set, having the diagnostics in order, and uniformly redundant, is very
helpful and lessens the possibilities of mistakes.

When I do network troubleshooting, I like to work from the bottom up, following
the OSI model.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

But I do see some things that you will want to check. One reason for "name not
found" is timeout while waiting for name resolution. This can happen on
computers with complex protocol stacks, such as IPX/SPX and NetBEUI. If you
have an unbalanced LAN - some computers with multiple protocols, and others
lacking some protocols, this can be a problem too.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

And the old LSP / Winsock corruption can cause "path not found" too.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html


ping 192.168.1.2
Click to expand...
Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
ping dh16mm51
Click to expand...
Pinging dh16mm51 [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
net view \\192.168.1.4
Click to expand...
System error 51 has occurred.

Windows cannot find the network path. Verify that the network path is
correct and the destination computer is not busy or turned off. If Windows
still cannot find the network path, contact your network administrator.
net view \\optiplex320
Click to expand...
Shared resources at \\optiplex320

MEREDITH

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
Printer2 Print Adobe PDF
Printer3 Print Xerox WC M20 Series PCL 6
Printer5 Print Dell Laser Printer 1700n
SharedDocs Disk
The command completed successfully.
net view \\192.168.1.2
Click to expand...
System error 53 has occurred.

The network path was not found.
net view \\dh16mm51
Click to expand...
System error 53 has occurred.

The network path was not found.
ipconfig /all
Click to expand...
Windows IP Configuration

Host Name . . . . . . . . . . . . : optiplex320
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controller
Physical Address. . . . . . . . . : 00-13-72-39-14-6F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Monday, May 07, 2007 2:37:28 PM
Lease Expires . . . . . . . . . . : Monday, May 07, 2007 3:37:28 PM
net config server
Click to expand...
Server Name \\OPTIPLEX320
Server Comment MEREDITH

Software version Windows 2002
Server is active on
NwlnkIpx (000000000001)
Nbf_NdisWanNbfOut{E57CF9F4-9AEA-4EFC-99D1-C4C1D633B8BF} (2ade20524153)
Nbf_NdisWanNbfOut{22BB62AD-7B9A-4865-8E52-997DA6AB16EE} (2ade20524153)
Nbf_NdisWanNbfIn{0E8257D2-0653-4C6E-B875-31BD88F2062E} (2ade20524153)
NetbiosSmb (000000000000)
Nbf_NdisWanNbfOut{3439A0D7-D43E-49BA-B85C-425CF0C09F5E} (2ade20524153)
Nbf_NdisWanNbfIn{8FC99D47-DBB0-4C5C-8E06-F03E191AE3C8} (2ade20524153)
Nbf_NdisWanNbfIn{E29424C1-CF03-4A8C-8136-14CE96565834} (2ade20524153)


Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.
net config workstation
Click to expand...
Computer name \\OPTIPLEX320
Full Computer name optiplex320
User name VPSI Houston

Workstation active on
Nbf_NdisWanNbfOut{22BB62AD-7B9A-4865-8E52-997DA6AB16EE} (2ADE20524153)
Nbf_NdisWanNbfIn{0E8257D2-0653-4C6E-B875-31BD88F2062E} (2ADE20524153)
Nbf_NdisWanNbfIn{E29424C1-CF03-4A8C-8136-14CE96565834} (2ADE20524153)
Nbf_NdisWanNbfIn{8FC99D47-DBB0-4C5C-8E06-F03E191AE3C8} (2ADE20524153)
Nbf_NdisWanNbfOut{3439A0D7-D43E-49BA-B85C-425CF0C09F5E} (2ADE20524153)
Nbf_NdisWanNbfOut{E57CF9F4-9AEA-4EFC-99D1-C4C1D633B8BF} (2ADE20524153)
NetbiosSmb (000000000000)

Software version Windows 2002

Workstation domain VPSI
Workstation Domain DNS Name (null)
Logon domain OPTIPLEX320

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.
browstat status
Click to expand...
Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfIn{0E8257D2-0653-4C6E-B875-31BD88F2062E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfOut{E57CF9F4-9AEA-4EFC-99D1-C4C1D633B8BF}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfOut{3439A0D7-D43E-49BA-B85C-425CF0C09F5E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfOut{22BB62AD-7B9A-4865-8E52-997DA6AB16EE}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfIn{8FC99D47-DBB0-4C5C-8E06-F03E191AE3C8}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain VPSI on transport
\Device\Nbf_NdisWanNbfIn{E29424C1-CF03-4A8C-8136-14CE96565834}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Is there any other information that is needed?
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Cannot connect to shares on Windows XP computer 2
XP - Win2K network problem 9
WinXP Pro & Win2K Pro Network - Help, or the computer gets it 2
Networking XP & Home PC with Cross wire 5
Shares inaccessible 3
WINXP Home/Professional Network PING problem 5
1 XP home machine can't access 1 XP Pro machine's shares / printer sometimes 1
File Shares between XP PRO and HOME 5

Top