Setup Trust between laptop and home network

  • Thread starter Thread starter mark
  • Start date Start date
M

mark

Hi all. I've got a laptop that I bring home from work that I'd like to
have access the resources (printer!) on my home network. My home
network is a NT2000 domain. When I come home I logon to my laptop
using the login for the domain I use at the office. Since it cannot
connect to the office PDC when I'm home I assume it using some caching
logic to authenticate (?).

So when I'm logged in to my laptop for a domain that really doesn't
exist (as far as my home is concerned) how can I have my laptop access
the resources on my home network?

I started down the path of having my home network trust the domain that
my laptop login is for but it complained when I tried to setup the
trust saying "The ZZZ domain could not be contacted?
Any ideas?
thx
mark
 
Whatever you do, don't try to "unjoin" or change domains for your laptop as
you may lock yourself out in the process. You can map drives and create
shortcuts to connect to your home computers or use your home domain
credentials if you receive a credential prompt. The key is that you will
have to use your username in the format of " domainname\user or
computername\user depending on if you want to authenticate to a domain
account or local computer account.

You will probably find that you are going to have to create local user
accounts on the home computers where you want to access shares since it is
not possible to create a trust between the domains. Then you can access a
share by mapping a drive as in " net use * \\computername\share
user:computername\username " and you will be prompted for the password for
that user account on the resource computer. After that you will find a drive
mapped in My Computer to the next available drive letter. You can make such
a mapped drive persistent but your laptop will complain every time you boot
at work because it can not locate the share. --- Steve
 
Your corp config has very possibly removed the ability to define
cached credentials else defining homedomain\youraccount as
what should be used when going to a machine in *.yourhome.local
domain would be one route you could use.
As it likely is, if you had a batch file that issued
\\server1\printer$
\\server2\share1
or whatever for the couple main servers you would be accessing,
then once you had logged in to the returned prompts with your
(home) domain account then future accesses to these machines
would piggyback over these established connections and so seem
fairly transparent.
 
Back
Top