Network path not found

[hgay]

My desktop workstation running XP-Pro joined my domain
running Windows 2000 Advanced Server and can access
resources on the server.

My server can ping the workstation using its DHCP-assigned
IP address or its FQDN.

The drives on the workstation are shared to administrator
and others who need access to the files.

But the server cannot cannot access workstation files.

I can see the computer under Network/Entire
Network/Microsoft Windows Network/domain but receive the
message "\\computername is not accessible. The network
path was not found." when attempting workstation access.

The computer name shows up in WINS and DNS pointing to its
IP address.

How can I gain access to the workstation shared files?

 

[Brennan Crowe [MSFT]]

Harold,

Check the permissions on that folder you are trying to connect to. Make
sure that your user on XP has those permissions. Try to create a new share
and see if you can connect to it. From the XP client, open a command prompt
and type "Net View \\server". where "server" is the name of the server you
are trying to connect to. What do you see?

--
Thank you,

Brennan Crowe
Microsoft corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[x]

My desktop workstation running XP-Pro joined my domain
running Windows 2000 Advanced Server and can access
resources on the server.

My server can ping the workstation using its DHCP-assigned
IP address or its FQDN.

The drives on the workstation are shared to administrator
and others who need access to the files.

But the server cannot cannot access workstation files.

I can see the computer under Network/Entire
Network/Microsoft Windows Network/domain but receive the
message "\\computername is not accessible. The network
path was not found." when attempting workstation access.

The computer name shows up in WINS and DNS pointing to its
IP address.

How can I gain access to the workstation shared files?

I get the same thing here, and I found a simple work around is to simply
input the system's IP address instead of the Computer name when Mapping the
drive. No, it's not ideal, but it doesn't adversely affect anything else the
systems here are doing, and I don't have time to figure out why the name
resolution isn't working properly.

This is of course assuming that your problem is the same as mine. It might
not be.

 

[Harold]

Brennen,

In this case, the XP workstation is the file server. XP
can access files on the 2000 server but not vice versa.

Both systems have administrator privileges.

Typing net view \\server on the XP workstation shows all
shared resources on \\server. Typing net view
\\XPworkstation on XP workstation shows all shared
resources on \\XPworkstation.

Typing net view \\server on 2000 server shows all shared
resources on 2000 server.

--BUT-- typing net view \\XPworkstation on 2000 server
does NOT show any shared resources for XP workstation.

i.e., when trying to access shared resources on the XP
workstation from the 2000 server, I receive the
message "network path was not found." No shared resources
are listed.

This despite I can ping the workstation, I can ping the
workstation using \\workstation and the FQDN which decodes
to the proper IP address, and the workstation is listed in
WINS and DNS with proper IP address.

I tried deleting and recreating a new share on the
workstation ("C" for drive C) and, when that failed, tried
creating a second share on the workstation ("CC" for drive
C).

Best regards,

Harold