General discussion

Locked

Can't map network drive

By Paland ·
I have a computer that I have recently upgraded to Win98 and it's networked on an NT domain (NT 4.0 are the servers. When I try to add a new network printer, it tells me that the name of the printer is already used, and to select another. It doesn'tmatter what name I use it will still say the same thing. I currently have no printers defined. .
Whenever I try to map a network drive (doesn't matter which), I get a dialog saying "F: is already connected to ." "Do you want to connect it to <drive> instead?"
If I click on yes, I get the same dialog over. If I click no, the operation is cancelled. I can access these folders through network neighborhood, I just can't map them. It doesn't matter which drive letter I use (E to Z). Does anyone know anything about this?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Can't map network drive

by Xanderoth In reply to Can't map network drive

Hmmm, what a fun one! Ok, here is what I would try. REBOOT! Woo hoo! Ok, now on to real answers...
1.Try using the net use command in a command prompt.
2.Setup a logon script on the NT server to map your drives and printers at logon.
3.Shutdown your computer. Go into Server manager on NT server, remove your computer and user from connected users and from computer lists. Then restart your 98 machine and log back in and try again.
4.If you dont log into the server, try logging intothe server. :)

If all else fails...
5.FDisk, Format and Forget it. :)

Collapse -

Can't map network drive

by Paland In reply to Can't map network drive

#1 we tried. And as for #2-3, It might work but the network administrator will not do anything on the server. It's up to me to either figure it out or wipe it clean and start over. I'm going to give it another day to try to figure it out. I did get rid of the Client, adapter, and protocol and rebooted. Then setup the TCP/IP again but I still have the same problem.

Collapse -

Can't map network drive

by geoSEAN In reply to Can't map network drive

This error can occur if the drive letter you are trying to map is higher than the last drive available to Windows. The last drive available to Windows is defined in the LASTDRIVE= statement in the CONFIG.SYS file. For example, this error occurs if you try to map drive F, but the CONFIG.SYS file contains the statement LASTDRIVE=E

Good Luck!

Collapse -

Can't map network drive

by Paland In reply to Can't map network drive

Lastdrive=Z, I had no config.sys but I did add it in case and it still didn't work. The windows registry has a last drive listed as Z as well.

Collapse -

Can't map network drive

by Paland In reply to Can't map network drive

This question was closed by the author

Collapse -

Can't map network drive

by Paland In reply to Can't map network drive

I found the problem, (or rather, another co-worker did). Our interdrive client was interfering somewhere. When we uninstalled InterDrive and then rebooted, we then could access the drives again.

Back to Windows Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums