4 replies
by joseph moore
I have had to deal with traveling employees plugging into different networks.
DHCP is the answer.
Have the network cards in these laptops be using DHCP for their IP assignment, not static IPs.
So, they go to a client site, plug a CAT-5 into the client's network, boot up, and they are assigned an IP by the client.
That takes care of addressing. Now, when it comes to rights on the client's network, that does get trickier. I suggest that the engineers do NOT remove themselves from your company domain; they should either log into the laptops with their normal domain user name/password OR a local machine user name/password (that only exist on the laptops own list of users). If the engineers choose to use the account from your domain, then they will get the authentication error about no domain controller found. That is ok. They will log into the 2000Pro laptops with cached login info. No big deal there.
Now, when they need access to client network devices (shares, printers, etc), the client administrator can set up a user account that your engineers can use only for drive mapping and printer sharing purposes. If your engineer needs to access the client's SHARED folder on \\CLIENT1 server, then have the client admin make a user account with rights to the share.
Then, instruct your engineers how to make a drive mapping with the "connect using a different user name" option. In this option box, they can specify the client domain/user name and password the client admin set up for them.
by joseph moore
.
.
The same type of thing can be done with client printers. The best way I have found of connecting to a printer in Win2K that belongs to a different domain than your machine account exist in is to browse to the printer in My Network Places, or to just open a Run box and type in \\CLIENT_PRINT_SERVER_NAME
The engineers will get a login/password challenge box when they do this. Just have them put in the client domain\user name and password in the box that the client admin makes for them.
That will allow the engineers to browse all shared items, including printers.
Then, have the engineers double-click the shared printer they want to print to. That will start the printer install under the security credentials of the client domain username and password.
The whole point of this is that traveling engineers do not need to change their machine domain membership when they go from jobsite to jobsite. Just keep their memberships as they are when they are in your office, and have the client admin set them up. Also, teach your engineers what they need to do to connect.
Switching their laptops out of your domain, and having to build the accounts when they are in your office later, is not needed.
by shanghai sam
by ppkehoe
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending