Map Network Drive

I would check the identification of that workstation. Right click network neighborhood on your desktop. Choose properties... Click Indentification tab. Is the computer name and description correct ? Is the workgroup correct ? Good luck. Hope this helps.

tech4life@core.com

Are the other workstations win9x or winnt?
if they are windows nt the problem might be because of the 8.3 limitation in win9x. Create a new share within the 8.3 limits.

Hi,

If you want to MAP network drives, it must be done on the SERVER, not the workstations.

Make sure the workstations all have a uniques share name, not just the default name. Example: drv-C-Sales then it will map automatically to a new network drive such as "F" or perhaps "G" depending on how many drive letters you have already used on your NT server.

Hope this gets you started in the right direction.

Regards
George

Additionally, you should go to Server Manager, and insure that each workstation has been JOINED to your servers DOMAIN.

Cheers

I think DS9 is on the right track, but I'll offer a little more...

I gather that you are trying to map a drive on the workstation, to the server. If this is the case, you have to make sure that on your server you have shared the particular driveor folder, and assigned the appropriate permissions. The permissions part is important, as Windows NT employs the most restrictive permission set within a tree of folders.

Also in Server Manager, check out your server - there should be a Shared Directories menu option, which lists all your shares. By default, all installed drives will show up in the Shared Directories list as $ - which is a System and Administrator share. A Windows 9x machine will not typically be able to map a drive letter to C$ - therefore you need to actually share the drive, or create a folder and share it.

For example, on your server's C:\ drive you create a folder called \ALLDATA, and you share the folder. You set permissions for the \ALLDATA folder for the Everyone global group to have read & write access. Then you can go to the client PC, log in to the domain, browse through network neighborhood to the \\\ALLDATA folder and map a drive.

Good luck!

(i'm assumming your using tcp/ip) try pinging the name, if that doesn't work then your network setup is jacked up.

This workstation must be logged on in order to "see" other shares.

Can you see all the machines on your network through network neighbourhood ?
If not (I know this sound silly)go into properties of network neighbourhood and change the workgroup name to the domain name
I dont know why this affects things but it does on our domain.

OK, one of the other answers you rejected, yet replied to might offer me some help with diagnosis.

If you are running TCP/IP, on your NT server, you should flush out your WINS cache. Your WINS database can sometimes collect more than the normal three entries for each client which confuses the name service, and therefore cause problems connecting to other machines on the network. Clear your WINS database, and allow it to refresh, and I recommend doing this after hours, so that the workstations will refresh their registrations upon the next login.

One other possibility, the TCP/IP stack on your workstation might be corrupt. If the above doesn't solve your problem, try reinstalling the wsock32.dll and winsock2.dll files from your Win98 CD-ROM to C:\Windows\System folder and restart your computer. This should cure problems with your TCP/IP stack.

Good luck!

This question was closed by the author