Discussion Locked

XP Pro can't access W2K server share

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Windows NT 4 network with a few W2K member servers on it. I just put our first XP Pro client on the network and when I try to access shared folders on any of the W2K servers, I get the following error message: \\"W2K Server Name" is not accessible. You may not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
I am a domain admin and this is my computer so I know I have permission. Also, I can't map tothe administrative share on any of the W2K servers but can on the WinNT servers. I even specifically shared a folder on one of the W2K servers and gave myself full access to the folder but I still can't connect to it. I don't understand why.

6 replies

by gigelul

Hi,
You tried set the permissions from an Win2k or NT system and then check from WinXP if you can access this share?
I had the same problem when I try to set permission from Win2k to NT Server. Generaly this is not a problem but I don't find wich caused this for me.

by gigelul

Also I suppose as you say that you have XP Professional edition and not Home edition which is very limited for joining in to a domain.

by swomack

Thanks for the response. I set the permission on the share from the W2K server but still could not access the share thru network neighborhood or thru map network drive. Also, it is XP Pro not Home edition. However, Answer 2 has helped by using the ip address of the W2K server instead of the name. I don't really understand why but perhaps when we move to native mode, this will change. If not, I will continue to use the ip address.
Thanks again.

by pmirlekar

setup dns server for your internal network .
put that dns ip in xp system.
can u ping to w2k ? try using \\ip address of w2k

by swomack

Thanks a bunch! When I use the ip address of the server I can map to the admin shares on that server. Now can you explain why? I am sure it has something to do with netbios or wins or dns but don't know exactly what. Perhaps when we move to ADor native mode the problem will be resolved.
Thanks again.

This discussion is closed to new replies.