Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Levien van Zon on October 22, 2003, 07:46:24 PM
-
Hello Everyone,
Yes it's yet another episode in the continuing quest to connect a laptop running Win XP Professional to a SAMBA domain running on SME 5.5....
The problem is as follows: The first time I tried to connect the thing, it wouldn't see the PDC. After searching and asking around on this discussion board and trying a lot of different things I finally decided to reinstall XP completely, with exactly the same settings as before. Strangely enough, it worked.
However, a new problem seems to have come up. The machine now sees the domain and the PDC, but still refuses to be added to the domain. I've read all the manuals, FAQ, HOWTO's and taken all the usual precautions, patched the registry, etc. etc. I've tried various ways of adding the machine to the domain:
1) Opening the network-identification dialog, clicking 'change', selecting computername and domain (not the same name as workgroup), clicking OK, entering 'admin' as user account with the relevant password, clicking OK... XP then simply replies with: 'Access denied'.
2) Opening the network-identification dialog, clicking 'network id', going through the network-id-wizard, entering all relevant information, accounts, etc. XP then says: 'Error joining the domain: unknown username or invalid password'.
I've tried adding the machine-account to the server manually, as described in various SAMBA-HOWTO's (plus sending the appropriate event to the SME-server and restarting the SAMBA services). It still doesn't help.
Frankly, I'm at a loss as to what to do next. Any ideas anyone?
I don't have a clue as to why XP Pro won't let me connect to the domain - I've added Win2k, Win98, Win95 and Linux machines before without problems.
Does anyone know what's going on, or what else I could try?
Regards,
Levien
-
Have you add the regedit thingy under /home/e-smith/files/server-resources/regedit??
type http:///server-resources/regedit/ just use the winxplogon.reg
-
Try disjoining the domain first, ie make it a member of a workgroup rather than the domain, make sure all connections are disconnected ie drive mappings and printers, apply the XP reg patch and then try to join the domain.
> entering 'admin' as user account with the relevant password,
You should use a valid user account that exists on the sme server, then in the next screen use admin for the user allowing permission to join to the domain.
Ray
-
Hi Ray,
Ray Mitchell wrote:
> Try disjoining the domain first, ie make it a member of a
> workgroup rather than the domain, make sure all connections
> are disconnected ie drive mappings and printers, apply the XP
> reg patch and then try to join the domain.
Yep, did that. I used 'net use \server /delete' just to be sure that all connections were closed (there were none, so that was OK), and the computer was joined to a nonexistent workgroup.
> You should use a valid user account that exists on the sme
> server, then in the next screen use admin for the user
> allowing permission to join to the domain.
Tried that as well, didn't work. It still says invalid account or password.
Thanks,
Levien
-
http://forums.contribs.org/index.php?topic=18185.msg71335#msg71335
Read this post. It solved my troubles with the same issue.
good luck
-
Yes, I have to agree with Levien here, this would have to be THE biggest nightmare invloved with SME. I've had boxes that wont work using admin to join but will work using root. My experience is dont even try to put an XP box on the domain unless it's a brand new install and the XP box is connected to the network during the install. This seems to be the least painful way of doing things. Just my $0.02 worth.
-
Levien van Zon wrote:
> Yes it's yet another episode in the continuing quest to
> connect a laptop running Win XP Professional to a SAMBA
> domain running on SME 5.5....
You're using a quite old version of samba (on an unmaintained version of SME) to talk to a quite new version of Windows. It's not surprising that you have problems. I'd recommend you upgrade to SME 6.0b3 plus updates.
Charlie
-
> You're using a quite old version of samba (on an
> unmaintained version of SME) to talk to a quite new version
> of Windows. It's not surprising that you have problems. I'd
> recommend you upgrade to SME 6.0b3 plus updates.
I agree with Charlie's recommendation to upgrade to SME 6b3, but it isn't necessary to get XP to connect. PDC functionality in Samba 2.2x hasn't changed a great deal in some time. The version that is running on SME 5.5 will accept windows XP logins. Make sure you apply the registry patch for XP that allows it to join Samba domains: http://mirror.contribs.org/smeserver/contribs/dmay/mitel/howto/samba-howto.html
If you get the message that your client can't find the domain in question, chances are you have some type of a networking issue. Samba is seldom to blame for this error unless it isn't setup correct, which is should be if you haven't modified anything on SME.
To test WINS name resolution, issue the following command from your Win XP client.
nbtstat -a PDC_hostname
Here's what I see:
c:\nbtstat -a server
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
SERVER <00> UNIQUE Registered
SERVER <03> UNIQUE Registered
SERVER <20> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered
LEIINC.COM <00> GROUP Registered
LEIINC.COM <1B> UNIQUE Registered
LEIINC.COM <1C> GROUP Registered
LEIINC.COM <1D> UNIQUE Registered
LEIINC.COM <1E> GROUP Registered
MAC Address = 00-00-00-00-00-00
Regards,
Greg Zartman