Topic: Problem adding Win XP Pro to domain

[Levien van Zon]

Good afternoon everyone!

Yes, another XP related question (apparently I am not the only person
who has trouble with this quite horrible operating system

The problem is this: Every time I try to add a laptop running Win XP Professional
to our network domain, XP complains that it cannot connect to the Domain Controller for this domain.
The network connection can hardly be the problem, as the laptop can talk to our SME 5.6 server just fine, and I followed all instructions I could find in the SME manuals, this phorum and the Samba upgrade HOWTO at http://mirror.contribs.org/smeserver/contribs/dmay/mitel/howto/samba-howto.html.
I applied the patches for XP and made sure all NetBIOS server connections were closed and the workgroup was set to something nonexistent before trying to add the server to the domain.

The error was as follows (translated from Dutch):

DNS-name doesn't exist.
(foutcode 0x0000232B RCODE_NAME_ERROR)

Query was for SRV-record of _ldap._tcp.dc._msdcs.vossiusstraat.

As was to be expected the Windows Help was hardly helpful,
anyone any ideas as to what I'm doing wrong?
I added Windows 2000 machines to this domain before without
problems, I don't understand why this one won't add...

Regards,
Levien

[Peter]

At last I might be able to help someone!

http://forums.contribs.org/index.php?topic=18185.msg71335#msg71335


This is a post I made a little while ago, but one of the replies also adds value.


Hope this fixes your problem.

Peter.

[brian kirk]

Have just spent all day trying to make 3 XP Pro machines join a domain. One joined without problems after the reg fix. The other two with all relevant settings identical to the first adamantly refused to find the domain controller. In desperation I reinstalled XP Pro, gave all the same settings during setup that they originally had and after the reg hack they joined the domain.
Go figure.
I think Mr Gates deserves a bill for 8 hours of wasted time
Regards
Brian

[Levien van Zon]

> At last I might be able to help someone!
> http://forums.contribs.org/index.php?topic=18185.msg71335#msg71335
> This is a post I made a little while ago, but one of the replies also adds > value.

Thanks for the reply! It's not going to help much I'm afraid, as I already
applied the registry patches - makes no difference. The problem seems to be somewhere in the way XP handles DNS lookups (I guess?).

Reinstalling XP might be an option, as Brian suggested, although
I'd rather not do that (would cost a lot of time to reinstall all software, backup files, etc.)

Regards,
Levien

[k_graham]

A year ago I had this difficulty on a win2000 pro system when I had already joined as if it was a workgroup. Solution was to delete all previous shares such as drive letters set up to ibays.

Of course when one re-installs windows they in effect do the same thing and voila it works.

Now if anyone can tell me my problem with why my 1 Mac can't hook up.

Ken

[k_graham]

A year ago I had this difficulty on a win2000 pro system when I had already joined as if it was a workgroup. Solution was to delete all previous shares such as drive letters set up to ibays.

Of course when one re-installs windows they in effect do the same thing and voila it works.

Now if anyone can tell me my problem with why my 1 Mac can't hook up.

Ken

[Levien van Zon]

k_graham wrote:
 
> A year ago I had this difficulty on a win2000 pro system when
> I had already joined as if it was a workgroup. Solution was
> to delete all previous shares such as drive letters set up to
> ibays.

This one was indeed also added to the workgroup before,
by someone-else who also couldn't get it to connect to
the domain. However, I'm pretty sure I disconnected
all SMB-shares and changed the workgroup name before I
tried to connect the thing to the domain (as the HOWTO
instructs as well). I'll check though, just to make sure I
haven't overlooked something...

> Of course when one re-installs windows they in effect do the
> same thing and voila it works.

That could indeed be true. Brian, the 3 XP machines you tried
connecting, were they freshly installed or had they been
connected to a/the domain as a workgourp before?

Regards,
Levien

[brian kirk]

In my case the XP machines were fresh installs and I checked there were no shares before I tried to join the domain.
Regards
Brian

[k_graham]

3 other difficulties I have thought of.

The simple one is that e-smith does not allow - administrator - as as user because it is 1 character too long and it being the standard for Windows is easily tried.

2nd is names need to be lower case I think.

3rd is that XP seems to want to autofind printers so I am guessing a share might be created  without realizing it.

As a user and not a network guru I still have difficulties seeing a lot of value in a domain vs a workgroup. It does store a batch file that one can set up for network and printer connections on the server. However if the server is down where are you. No wonder its desired to have two domain controllers in Windows. Probably its a matter of security more than anything.

On a workgroup one can create a batch file and put it in the startup directory of each computer so drives and  printers hook up the same each time and if one server  is  down you still may have some functionality. example

net use lpt1: \server2\hpprinter
net use s: \server\dataebay

[Walter Padgett]

Good Evening,

Looks like the same mulberry bush.

http://forums.contribs.org/index.php?topic=18287.msg71766#msg71766

Since I've been putting these SME 5.6 servers everywhere in the school district that I work in, I've come across various issues. I've figured out the share thing as well as the printer thing. I'm not quite sure about the roaming profile issue. I seem to be having some issues with that.

The one thing that I would really like is to specify a different login script for either a specific user or a specific group. Haven't quite figured that one out yet. I don't really like putting everything in one netlogon.bat file with all the variables trying to detect this or that.

Concerning the MAC issue, doesn't SME load Appletalk? It should be pretty straightforward concerning this I would believe.

BTW, the above mentioned thread has a reghack that I've used with great success.

Later,

Wally

[Levien van Zon]

Well...
After trying just about every trick I could think of, I still couldn't get the XP-machine to find a PDC. In the end it seemed easiest just to reinstall XP, as Brian suggested. And lo and behold, it worked! At least, it solved problem #1, finding the PDC. XP still won't let me actually add the machine to the domain, but at least it can now *see* the damned thing.  It now complains that either I am using the wrong type of account ("The account supplied is a computer account"), or just says "Access denied" when I try to add the box to the domain, but I'm pretty sure that it should be relatively "easy" to sort out.

Regards!
Levien

[dgpwalker_at_optusnet.co]

I had the same issues with Win XP Pro. Only thing I did was to create a new user account as there was some 'issues' with mine. ~The newly created account worked fine from login.

Only now I try to add my machine to the domain, and after windows approval and a reboot, there was an error stating a problem with trusts?

Did anyone come across this and if so what caused it / fixed it?

[Brad D.]

Did you  run the reg fix? It is *needed* before getting xp/2k to connect to the SME domain.

[dgpwalker_at_optusnet.co]

I made a couple of reg fixes, which worked, but during login a message reports that it 'cannot find the roaming profile for this user' then another appears saying that 'You'll be logged in using temp profile' which is of no use to me.
Roaming profiles is turned off on the server manager, so just in case I missed something in the registry,I added .../regedit/winxplogon.reg but still got shot down with the same error messages.
What have I done wrong?! I can't find an answer for this one...
Anyone know the answer?

...Dave

Brad D. wrote:
>
> Did you  run the reg fix? It is *needed* before getting xp/2k
> to connect to the SME domain.

[Henrik]

There is a roaming profile bug in v5.x... Mitel knows this cause they solved the problem due to my bug report. But they will not issue a fix for any v5.x versions they said in an e-mail to me... Made me kinda sad, cause i reported it as a bug in 5.6 and they fixed it in 6.0... sux big time i think.

So u will have to install V6.0b3 and all the updates to get rid of it...