Cannot connect to computer not joined to domain

[Erik Tamminga]

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

 

[Michael Giorgio - MS MVP]

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]

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]

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

 

[Phillip Windell]

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.

 

[Michael Giorgio - MS MVP]

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..

 

[Erik Tamminga]

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

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

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" <[email protected]> schreef in
bericht news:%[email protected]...

 

[Erik Tamminga]

See my reply to Phillips' reply.

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?

 

[Phillip Windell]

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.

 

[Michael Giorgio - MS MVP]

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?

 

[Michael Giorgio - MS MVP]

The exact message is e.g., . No logon servers
available to authenticate your logon request?

 

[Doug Sherman [MVP]]

You will have much better luck with this if you log onto the local machine
instead of using cached domain credentials. When the logon screen comes up,
click the Options button and select the computername. You will need a local
user account on the laptop to do this - preferably a member of the local
administrators group.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

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

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

message news:%[email protected]...

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

ask

me schreef
in

 

[Dave]

go

this case is an easy one to fix. first the customer's drive or appropriate
folder must already be shared. then you map a drive to their share and
select the option to connect as a different user. have one of the users who
has appropriate access to the machine do the login with their
domain/username and password, then you have access to the share until you
disconnect or shutdown.

 

[Steven L Umbach]

Keep in mind that XP Home is quite a bit different that XP Pro and W2K. It
uses simple file sharing and everyone authenticates as guest to access a
share. So first make sure that the guest account is enabled in XP Home in
Control Panel/user accounts - guest. Then you need to create a share which
will prompt you to start the network sharing wizard or just bypass it and
share the folder. Note that the networking wizard will probably enable the
built in ICF firewall which you make sure is disabled when you are done
setting up sharing. --- Steve

 

[Steven L Umbach]

Oops. I was wrong in that the guest account does not need to be enabled on XP Home,
but file and print sharing needs to me enabled by creating a share. -- Steve

 

[Erik Tamminga]

Hi michael,

Yes the exact message is "there are currently no logon servers available to
service the logon request". I notice there are a lot of messages posted on
the internet about this error, but none give me a satisfiable answer.

The problem is my laptop has numerous applications installed (together with
their settings/profiles). I do not want to login locally because this gives
me a complete different set of setting/profile in which the applications I
use do not work as expected.
Whenever I travel to one of my customers to offer them support I connect to
their network and would like to transfer some files to their servers. I can
browse the network and see the server, but whenever I double click the
server I get this message.
If I do a "net use \\server /user:username" in advance everything works
fine. Now what I don't understand is why I'm not asked to enter my
credentials when connecting to the server via the windows explorer.

Erik