"Jonas Nielsen" <> wrote in message
news:4b13b6b8$0$272$...
>I am trying to test active directory log in on a network with a linux
> dns and dhcp server.
>
> I have set up a windows 2003 server, and windows vista client. I now
> enter the name of the vista computer in Active Directory on the server.
> The server then tell me to use http://COMPUTERNAME/ConnectComputer so i
> type in http://<ip address of server>/ConnectComputer in a browser on
> the vista machine.
>
> It now runs a program called nshelp.exe. In that application I can now
> login using the AD administrator password. I can then assign different
> users to the vista client.
>
> However when I press next. It says "An error occured when configuring
> networking settings. See your network administrator".
>
> I have tried to look in the event viewer on the windows server but there
> is no related entries. Does anyone have an idea of what the error is
> and/or how I can find out.
Apparently this is SBS, and SBS questions are best suited for the SBS
newsgroup due to it's differences to regular Windows. Nonetheless, whether
SBS or not, it's still AD. If the client is not using the SBS as it's only
(ONLY) DNS address in it's IP config, then the connect and resulting join
will fail because it cannot "find" the domain controller.
Please post an ipconfig /all from the server and from the Vista client to
allow us to evaluate the config and provide a specific diagnosis.
With any AD infrastructure, all clients must only use the internal DNS
servers that either host the AD zone or have a reference to it (stubs or
secondaries), otherwise numerous things will fail.
You can use non-Windows DNS and DHCP, but to make it work properly, the
machines must only use that specific DNS server, including the SBS, and
making sure the zone is allowed to update. My feeling is if you setup SBS
properly, it would have pointed to itself for DNS, and it appears if that
was the case, the client is using the Linux box as DNS, therefore, I'm not
surprised of the join failure you are seeing. You must keep continuity with
DNS resolution in the infrastructure.
Using Linux as DNS as long as BIND is 8.2 or newer, you can do it, but keep
in mind, BIND does not support AD integrated zones (storing the zone
securely in the actual AD database and not as a text file), nor does it
support Secure Updates using Kerberos through AD. There are other advantages
using Windows DHCP as well including the ability to configure it to 'own'
any record it registers into DNS in order for it to update previously
registered records such as when a client gets a new DHCP lease with a
different IP.
It's really much easier to use Windows services for this. Things just work
with minimal involvement, and it is much more secure.
(cross-posted to the SBS newsgroup)
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Linear Mode
