Discussion Locked

How to map via RAS properly?

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

I have the same situation for three different locations. At one site, I set
up a user to dialin via RAS to an NT server, and fire up a database on his
local machine which points to the databases physical location to get the
data from the server. It works wonderfully. The customer is tickled how
using this method with existing phone lines saved them from having to follow
the software vendors recommendation to buy a 56k Lease line, CSU/DSU
routers, multiplexor's etc. (For a single computer at the remote site) They
wanted to use PC Anywhere and hook the printer, and the bar code scanner and
the PC each to the multiplexor. The cost would have been quite high. The
only problem we have is the vendor has the path of a mapped drive that
provides a copy protection check in a dongle. The path is a mapped location
such as:
Z:\thisdir\filename.exe

The way I implemented the connection, my map shows up as:
Z:\100.100.100.10\thisdir\filename.exe

Since this path doesn't match the path ha

7 replies

by bl1

Share the \thisdir folder. Map the z drive to the share. "Net use z: \\100.100.100.10\thisdir"

That should give you the z:\thisdir you are looking for.

by rindi1

If your customer is using win9x as his OS it is possible that you can't map drive Z: in the login script, as this could be the mapping windows is using while logging on to the network as a temporory share, to get login information from the server. Once logged in, this share gets released again and you can use it again. So, if you can't map your z: drive with a login script, use another drive letter, or run a batch file after he's logged in, which does the mapping.

by jcorlett

You may also want to use the /PERSISTANT switch for this mapping so it doesn't need to be re-entered every time the user reboots. Type at the command prompt for the correct usage.

This discussion is closed to new replies.