Workgroup and AD on the same network

[jabw]

Hi,

If I install AD/DNS on my W2k3 server than the next thing that happens is that some users that are in a workgroup on the same physical network (via a wireless Access Point) using the same gateway can't get anywhere anymore. (i.e. MSN can't be used anymore).

Can imagine that AD want to rule the network on all OSI levels but how is it doing this? If it is doing this.

Any suggestions?

 

[porkchopexpress]

They should coexist just fine.

Are the users having problems in a seperate workgroup logging on with local accounts?


You know what Jack Burton always says at a time like this...

 

[jabw]

{Quote}
Are the users having problems in a seperate workgroup logging on with local accounts?
{End Quote}

They do login using local accounts on a workgoup.
But before I moved the Sever to become an AD it was a member of the same workgroup!

Could that be the problem?

 

[porkchopexpress]

Are the clients still pointing to your AD/DNS server for name resolution?

Is you access point also your ADSL router?

You know what Jack Burton always says at a time like this...

 

[jabw]

Found the problem.
If the server is a member of the same workgroup as the other machines on my network and then I change the server to become an AD domain controller than the other machines in the workgroup don't work correct any more.

If the server is initally in a workgroup of its own, there is nog problem.

Solution. The server should never be part of an excisting workgroup before it becomes a DomainController.

Dont know why but this is what I found in a real life situation.