Cannot connect to computer not joined to domain

Hi,

At work we migrated from a Novell infrastructure to a Win2003 domain
infrastructure. All went fine and all office computers are now member of the
office-domain.

Now when I go home and take my laptop with me I cannot connect to my home-pc
(browse to a share) and windows complains about not being able to locate the
domain controllers to authenticate the request.

A "net use \\home-pc\c /user:homepc\myname" does work. Why doesn't windows
ask for a username/password when I connect to my home pc via the
explorer-gui?

Home-pc is a Windows XP Home edition (SP1, stand-alone, no domains)
Laptop is a Windows 2000 Professional (member of the office-domain).
Both are connected via wired-ethernet, no firewalls on either machines.

Erik

Hi Erik,

The W2k pro machine is a domain member which by
default authenticates against a domain controller. This
explains why it's looking for a DC during the logon
process. You can ignore the message and logon with
cached domain credentials or create a local account
and choose the computer name instead of the domain
during the logon process at home. There are third
party alternatives e.g., netswitcher which simplify
the process.

"Erik Tamminga" <REVERSE_THIS_agnimmate@REVERSE_THIS_nerrats.ln> wrote
in message ...
> Hi,
>
> At work we migrated from a Novell infrastructure to a Win2003 domain
> infrastructure. All went fine and all office computers are now member
of the
> office-domain.
>
> Now when I go home and take my laptop with me I cannot connect to my
home-pc
> (browse to a share) and windows complains about not being able to
locate the
> domain controllers to authenticate the request.
>
> A "net use \\home-pc\c /user:homepc\myname" does work. Why doesn't
windows
> ask for a username/password when I connect to my home pc via the
> explorer-gui?
>
> Home-pc is a Windows XP Home edition (SP1, stand-alone, no domains)
> Laptop is a Windows 2000 Professional (member of the office-domain).
> Both are connected via wired-ethernet, no firewalls on either
machines.
>
> Erik
>
>

Hi Michael,

The problem is not with logging in to the w2k machine, that works fine
(cached credentials).
After I login to the w2k machine I would like to browse a network share of
my home-pc.
This is when the problem occors. Windows presents me a message that my
credentials cannot be checked and does not present me a login-dialog.
Connecting to the share from within a cmd box using "net use ... /user:..."
does work. Now my question is: why doesn't the windows explorer gui ask me
for a username password?

Erik


"Michael Giorgio - MS MVP" <(E-Mail Removed)> schreef in
bericht news:%(E-Mail Removed)...
> Hi Erik,
>
> The W2k pro machine is a domain member which by
> default authenticates against a domain controller. This
> explains why it's looking for a DC during the logon
> process. You can ignore the message and logon with
> cached domain credentials or create a local account
> and choose the computer name instead of the domain
> during the logon process at home. There are third
> party alternatives e.g., netswitcher which simplify
> the process.
>
> "Erik Tamminga" <REVERSE_THIS_agnimmate@REVERSE_THIS_nerrats.ln> wrote
> in message ...
> > Hi,
> >
> > At work we migrated from a Novell infrastructure to a Win2003 domain
> > infrastructure. All went fine and all office computers are now member
> of the
> > office-domain.
> >
> > Now when I go home and take my laptop with me I cannot connect to my
> home-pc
> > (browse to a share) and windows complains about not being able to
> locate the
> > domain controllers to authenticate the request.
> >
> > A "net use \\home-pc\c /user:homepc\myname" does work. Why doesn't
> windows
> > ask for a username/password when I connect to my home pc via the
> > explorer-gui?
> >
> > Home-pc is a Windows XP Home edition (SP1, stand-alone, no domains)
> > Laptop is a Windows 2000 Professional (member of the office-domain).
> > Both are connected via wired-ethernet, no firewalls on either
> machines.
> >
> > Erik
> >
> >
>
>

Okay so when do you get the error message? Do
you see the home PC in My Network places? Do
you see the share?

"Erik Tamminga" <REVERSE_THIS_agnimmate@REVERSE_THIS_nerrats.ln> wrote
in message
> Hi Michael,
>
> The problem is not with logging in to the w2k machine, that works fine
> (cached credentials).
> After I login to the w2k machine I would like to browse a network
share of
> my home-pc.
> This is when the problem occors. Windows presents me a message that my
> credentials cannot be checked and does not present me a login-dialog.
> Connecting to the share from within a cmd box using "net use ...
/user:..."
> does work. Now my question is: why doesn't the windows explorer gui
ask me
> for a username password?

You can't do this because the Workgroup Name and the Domain name do not
match. Make your home Workgroup Name match the Domain name at work.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Erik Tamminga" <REVERSE_THIS_agnimmate@REVERSE_THIS_nerrats.ln> wrote in
message news:%(E-Mail Removed)...
> Hi Michael,
>
> The problem is not with logging in to the w2k machine, that works fine
> (cached credentials).
> After I login to the w2k machine I would like to browse a network share of
> my home-pc.
> This is when the problem occors. Windows presents me a message that my
> credentials cannot be checked and does not present me a login-dialog.
> Connecting to the share from within a cmd box using "net use ...
/user:..."
> does work. Now my question is: why doesn't the windows explorer gui ask me
> for a username password?
>
> Erik
>
>
> "Michael Giorgio - MS MVP" <(E-Mail Removed)> schreef
in
> bericht news:%(E-Mail Removed)...
> > Hi Erik,
> >
> > The W2k pro machine is a domain member which by
> > default authenticates against a domain controller. This
> > explains why it's looking for a DC during the logon
> > process. You can ignore the message and logon with
> > cached domain credentials or create a local account
> > and choose the computer name instead of the domain
> > during the logon process at home. There are third
> > party alternatives e.g., netswitcher which simplify
> > the process.
> >
> > "Erik Tamminga" <REVERSE_THIS_agnimmate@REVERSE_THIS_nerrats.ln> wrote
> > in message ...
> > > Hi,
> > >
> > > At work we migrated from a Novell infrastructure to a Win2003 domain
> > > infrastructure. All went fine and all office computers are now member
> > of the
> > > office-domain.
> > >
> > > Now when I go home and take my laptop with me I cannot connect to my
> > home-pc
> > > (browse to a share) and windows complains about not being able to
> > locate the
> > > domain controllers to authenticate the request.
> > >
> > > A "net use \\home-pc\c /user:homepc\myname" does work. Why doesn't
> > windows
> > > ask for a username/password when I connect to my home pc via the
> > > explorer-gui?
> > >
> > > Home-pc is a Windows XP Home edition (SP1, stand-alone, no domains)
> > > Laptop is a Windows 2000 Professional (member of the office-domain).
> > > Both are connected via wired-ethernet, no firewalls on either
> > machines.
> > >
> > > Erik
> > >
> > >
> >
> >
>
>

Phillip, I have an XP home PC on my home
network and I have no problems browsing
the MSHOME default workgroup from my
XP pro domain member using cached
credentials..

"Phillip Windell" <@.> wrote in message
news:%(E-Mail Removed)...
> You can't do this because the Workgroup Name and the Domain name do
not
> match. Make your home Workgroup Name match the Domain name at work.
>
>

Hi Phillip,

Well, my home-pc is used as an example. The same problem occurs when I go to
one of my customers and try to connect to their servers to transfer some
files. I can't change their workgroup/domain configuration just to copy some
files and also do not want to change my own domain settings.

My computer runs Windows 2000 professional with Sp4 and all (known) patches
applied. The message pops up when I click on the (remote-)computer in
network neighbourhood. The same message also pops up when I issue the
\\home-pc command in Start->Run.

Erik



"Phillip Windell" <@.> schreef in bericht
news:%(E-Mail Removed)...
> You can't do this because the Workgroup Name and the Domain name do not
> match. Make your home Workgroup Name match the Domain name at work.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> "Erik Tamminga" <REVERSE_THIS_agnimmate@REVERSE_THIS_nerrats.ln> wrote in
> message news:%(E-Mail Removed)...
> > Hi Michael,
> >
> > The problem is not with logging in to the w2k machine, that works fine
> > (cached credentials).
> > After I login to the w2k machine I would like to browse a network share
of
> > my home-pc.
> > This is when the problem occors. Windows presents me a message that my
> > credentials cannot be checked and does not present me a login-dialog.
> > Connecting to the share from within a cmd box using "net use ...
> /user:..."
> > does work. Now my question is: why doesn't the windows explorer gui ask
me
> > for a username password?
> >
> > Erik
> >
> >
> > "Michael Giorgio - MS MVP" <(E-Mail Removed)> schreef
> in
> > bericht news:%(E-Mail Removed)...
> > > Hi Erik,
> > >
> > > The W2k pro machine is a domain member which by
> > > default authenticates against a domain controller. This
> > > explains why it's looking for a DC during the logon
> > > process. You can ignore the message and logon with
> > > cached domain credentials or create a local account
> > > and choose the computer name instead of the domain
> > > during the logon process at home. There are third
> > > party alternatives e.g., netswitcher which simplify
> > > the process.
> > >
> > > "Erik Tamminga" <REVERSE_THIS_agnimmate@REVERSE_THIS_nerrats.ln> wrote
> > > in message ...
> > > > Hi,
> > > >
> > > > At work we migrated from a Novell infrastructure to a Win2003 domain
> > > > infrastructure. All went fine and all office computers are now
member
> > > of the
> > > > office-domain.
> > > >
> > > > Now when I go home and take my laptop with me I cannot connect to my
> > > home-pc
> > > > (browse to a share) and windows complains about not being able to
> > > locate the
> > > > domain controllers to authenticate the request.
> > > >
> > > > A "net use \\home-pc\c /user:homepc\myname" does work. Why doesn't
> > > windows
> > > > ask for a username/password when I connect to my home pc via the
> > > > explorer-gui?
> > > >
> > > > Home-pc is a Windows XP Home edition (SP1, stand-alone, no domains)
> > > > Laptop is a Windows 2000 Professional (member of the office-domain).
> > > > Both are connected via wired-ethernet, no firewalls on either
> > > machines.
> > > >
> > > > Erik
> > > >
> > > >
> > >
> > >
> >
> >
>
>

See my reply to Phillips' reply.

Erik
"Michael Giorgio - MS MVP" <(E-Mail Removed)> schreef in
bericht news:(E-Mail Removed)...
> Okay so when do you get the error message? Do
> you see the home PC in My Network places? Do
> you see the share?
>
> "Erik Tamminga" <REVERSE_THIS_agnimmate@REVERSE_THIS_nerrats.ln> wrote
> in message
> > Hi Michael,
> >
> > The problem is not with logging in to the w2k machine, that works fine
> > (cached credentials).
> > After I login to the w2k machine I would like to browse a network
> share of
> > my home-pc.
> > This is when the problem occors. Windows presents me a message that my
> > credentials cannot be checked and does not present me a login-dialog.
> > Connecting to the share from within a cmd box using "net use ...
> /user:..."
> > does work. Now my question is: why doesn't the windows explorer gui
> ask me
> > for a username password?
>
>

Ok,..well I'm not sure what to make of it then. I haven't dealt with that
exact issue, but in similar issues I always got a "login prompt" and then
just simply prefixed the username with the target machine name and used an
account that was locally on the target machine.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:uZ%(E-Mail Removed)...
> Phillip, I have an XP home PC on my home
> network and I have no problems browsing
> the MSHOME default workgroup from my
> XP pro domain member using cached
> credentials..
>
> "Phillip Windell" <@.> wrote in message
> news:%(E-Mail Removed)...
> > You can't do this because the Workgroup Name and the Domain name do
> not
> > match. Make your home Workgroup Name match the Domain name at work.
> >
> >
>
>

I agree I would expect a "login prompt" although I
do not recognize the error message. I am wondering
if the error posted is the exact error message the
poster is receiving?

"Phillip Windell" <@.> wrote in message news:
> Ok,..well I'm not sure what to make of it then. I haven't dealt with
that
> exact issue, but in similar issues I always got a "login prompt" and
then
> just simply prefixed the username with the target machine name and
used an
> account that was locally on the target machine.