Accessing Windows 2000 Shares

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm sure someone has run into this problem and found a way around it. We
have hired contractors that have their own company laptops that are trying to
access resources on our Domain. Problem is that the laptops they are using
belong to their companies domain, so when they try to access our shares it
fails because their laptops are trying to authenticate to their own domain.
Is there any way around this.
 
RealFastR1 said:
I'm sure someone has run into this problem and found a way around it. We
have hired contractors that have their own company laptops that are trying to
access resources on our Domain. Problem is that the laptops they are using
belong to their companies domain, so when they try to access our shares it
fails because their laptops are trying to authenticate to their own domain.
Is there any way around this.
Click to expand...

If the contractors' laptops are set up correctly then they can start
a session even while they are not physically connected to their
own network. If they cannot then this is something for their own
adminstrator to resolve.

If the laptops configured for DHCP then they will automatically
pick up an address as soon as they are connected to your
network. If they do not use DHCP then once more their
administrator has to fix this.

Lastly, they can connect to your shares by using credentials
that you provide them with. When they make a connection to
a share in Explorer, they must click "Connect using a different
user name". They must then enter a user name / password
that you create for them on your server. There is no need
for their laptops to be registered on your domain.
 
Actually, it is the computer that has the share that is receiving the
credentials from the laptop and finding that it (the server) can not
authenticate the user.

One way we have found around this is for the contractor user to use the
command:

net use \\yourserver\ipc$ * /user:yourdomain\username /persistent:yes

Then, since the command is persistent, the contractor doesn't have to repeat
the operation each time they logon to their laptop at your site.

The "*" causes the command to prompt the user for the password, which is
then obscured.

This works especially well for printer shares because the user does not get
a prompt for credentials when connecting to a printer, like they do when
connecting to a folder share.

If the contractor's laptops have Windows 2000 or later, the user should get
a prompt for credentials when accessing a share on your servers. They can
then key
yourdomainname\username

and the corresponding password to get access to the share. This doesn't
work if the laptop has Windows 9x.
 
Back
Top