Ali,
Sorry, only my post was incorrect. (Been working on Unix most of the day.) The mapping was working up until yesterday. There has been no configuration changes that I am aware of since it started showing this error. We only have 2 users that log in from remote modems and both now have...
Have been logging on through RAS via a modem, but recently get the message for the mapped drive.......
"The following error occured while trying to connect D:to //server/sharename
Windows cannto find the computer or share name. Make sure the computer and sharename is...
I agree that if this box was a PDC/BDC, life would be simpler. Unfortunately, to make this server a PDC, I believe I would have to reinstall NT. Not possible now.
I need to map drive letters to roaming users. These drive letters will vary depending on user. Unfortunately, we are not using NT in a Domain. Just as a standalone server in a peer to peer network. (No PDC/BDC's on network) Clients are various versions of Win95 and Win98. Can it be done?
Remember that Win95/Win98 clients have a problem seeing any shares that have more than 12 characters in their shared name. It is best to adhere to the 8.3 format when naming shares regardless of what the OS can see locally to avoid problems across the network.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.