Workstation doesn't log onto network

[David Bolt]

I manage a network where the users all supply their own machines. We have no
control over OS on older machines so a number of workstations are running XP
Home. Now, most of these work OK, but a couple do not seem to log on
correctly. Since for instance workstations need to make use of network
printers, this is a problem.
So, any ideas what to look for to see why some machines connect but others
don't until for instance I try to browse the network, at which point they
ask for a network username and password.
Server is Win2000 Advanced Server.
I have now got a Certification Authority working, just, if that is any help.
Thanks
Dave

 

[Steven Umbach]

A Certificate Authority would not be able to remedy your situation. A CA issues
user and machine certificates for such things as smart cards, EFS file
encryption, and L2TP vpn. I have no experience with XP home but I know that
users of XP home can not logon to a domain directly nor can the machine itself
join the domain. However if there is a user account on the domain controller
that has the same logon name and password that the user logons to XP Home, they
should be able to access the network resources that account has permissions to
without a credential prompt I believe. --- Steve

http://www.wown.info/j_helmig/wxphdoms.htm
http://www.microsoft.com/windowsxp/home/evaluation/overviews/xpindomain.asp

 

[Marina Roos]

XP Home is not able to join a domain, upgrade to XP-pro.

Marina

 

[David Bolt]

Steve,
I think this one is the answer. Although the account display name is the
same as an account name on the server, I think the actual name, used in
re-establishing connections, is different.
Now, do you happen to know a good way of getting all the settings from one
user profile to another? I am not at all convinced that the file and setting
transfer wizard is the solution since it seems to keep per user data for the
same users on the 'new' machine. What I want is a way of setting up a new
user with all the settings from an existing user, instead of having to
install all the applications all over again.
Thanks
Dave

 

[David Bolt]

Marina,
Some have, some won't yet. It costs under £100 for XP Pro OEM, it costs
about £150 for XP Pro Upgrade. People are not impressed with the additional
cost and since they bought the machines before they talked to me they didn't
know to tell their suppliers that they needed a machine for business use the
suppliers 'forgot' to mention that there was a difference.
Personally I think MS should be offering a Home to Pro upgrade at
considerably less then the one they currently offer, but that's their
marketing strategy and we have to live with it or move to MAC or Linux.
BFN
Dave

 

[Steven L Umbach]

Don't confuse the account user name with the logon name. Just make sure that the
actual logon name and password that a user uses to logon to their computer is exactly
the same in the Active Directory Users and Computers account for that user. There are
ways to copy profiles, but it differs from operating system. See links below for more
info, though I do not think you need to copy any profiles. -- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;811151 --- For XP.
http://support.microsoft.com/default.aspx?kbid=255095 -- W2K, must be logged on as
administrator.

 

[David Bolt]

Steve,
I'll check up on that in the morning.
Thanks
Dave

 

[David Bolt]

Steve,
Got a workaround for now. By mapping a drive and requiring it be restored on
logon, and supplying the appropriate username and logon, even XP Home will
re-connect to the network, even if logon to XP is under a different username
and password to the ones stored on the server.
Dave

 

[Steven L Umbach]

Yes that will work. Keep in mind that if the password is changed on the account that
it is mapped to the share will fail. That may seem obvious now, but three months from
now it might not be as obvious. Glad you got a solution. --- Steve