Hello Christian, I was reading this thread with interest and thought you could help me with a similar challenge.

I was wondering if there is something unique about Win2000 when setting it up as a server. I have been helping a friend with their office PCs. We upgraded all of the workstations except one (the Win2000 laptop) to XP home edition and have simple router network configurations. (we just map drives on the main server PC for the workstations) It has always been one-way where the Windows2000 laptop and other workstation PCs access the XP server.

We want to move the laptop to another location and set it up to act as a server when it is there. I have found that I am having difficulty setting up the Win2000 laptop as a server. I can share out the hard drive and the laptop can see all of the workstations in the workgroup that want to access it. However I cannot map any drives on the XP workstations to the Win2000 laptop, it tells me it cannot find the server.

Questions:

1. Is there something unique using a WIn2000 (NT) machine as a server I am missing?
2. Should I create the Windows XP "Network disk" from one of the workstations and update the WIn2000 laptop with it? When you setup a simple network in XP, I remembered that it always asks if you want to create a "network disk" for non-XP machines.
3. Can Win2000 be upgraded to XP if everything else fails?
4. Any other suggestions to try?

Thank you in advance

Kevin

Are you using XP home as it cannot see NTFS win NT or 2K drives

This post should be a new thread. To answer your questions:

1. The most important thing to take into account when mapping drives is whether you're using the name of the computer or its IP. In a 2000/2003 Active Directory domain environment client pcs will usually obtain IP addresses from a server at which point they will have their IP registered in DNS (computer name to ip). You are using workgroups and XP Home clients so you mapping by name will have problems depending on how IP is setup. If you are trying to map to the 2000 box by name then this is probably why you're having trouble. The most simple way around it would be to use IP instead of name.
2. No...don't need it.
3. Yes - but you don't need to.
4. Use IP instead of trying to browse through Network Places or using computer name.