Vista - adding vista to a 2003 domain problem

Please help, I have a simple 2003 server configured as a DC and DNS. I use my router for DHCP.

I can add my xp pro boxes no problems but I have just freshly installed vista 64 ultimate, I have enabled the local admin account and I'm logged in using it, but when I add to the domain it just comes up "login failure: unknown username or bad password" im using the domain admin account to add the vista box!

I have searched the web and cannot find anyone else with similar problems,
Can anyone help please?

Any errors in the event viewer? these search results may help,
System Errors
System error 1326 has occurred - Logon failure: unknown user name or
bad password System error 1331 has occurred - Logon failure: account current
disable ...
http://www.chicagotech.net/systemerrors.htm - Similar pages

Event ID 529
Description: Logon Failure: Reason: Unknown user name or bad password
User Name: user name Domain: client computer name Logon Type: 3 Logon
Process: KSecDD ...
http://www.chicagotech.net/troublesh.../event529a.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"insidesolutions_64U" <insidesolutions_64U.2pr2g7@no-mx.forums.net> wrote in
message news:insidesolutions_64U.2pr2g7@no-mx.forums.net...
>
> Please help, I have a simple 2003 server configured as a DC
> and DNS. I use my router for DHCP.
>
> I can add my xp pro boxes no problems but I have just freshly installed
> vista 64 ultimate, I have enabled the local admin account and I'm logged
> in using it, but when I add to the domain it just comes up "login
> failure: unknown username or bad password" im using the domain admin
> account to add the vista box!
>
> I have searched the web and cannot find anyone else with similar
> problems,
> Can anyone help please?
>
>
>
> --
> insidesolutions_64U

I have just looked at the event viewer on the vista machine and the only event that gets logged for this is a security audit which is succesfull.

Any other ideas? This is really bugging me

How about DC? Any errors?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"insidesolutions_64U" <insidesolutions_64U.2prh1c@no-mx.forums.net> wrote in
message news:insidesolutions_64U.2prh1c@no-mx.forums.net...
>
> I have just looked at the event viewer on the vista machine and the only
> event that gets logged for this is a security audit which is succesfull.
>
> Any other ideas? This is really bugging me
>
>
> --
> insidesolutions_64U

I have just attempted to add it again to the domain and then checked local DC logs and there are no problems, but there is no mention of me trying to contact the server to add the machine.

The only other thing I got wrong in my first email is the router that I'm using for my DHCP is also being used to look after the DNS.

I can succesfully ping the server name from the vista machine and I can map a drive to the server from the vista machine using the server name.

I have just attempted to add it again to the domain and then checked local DC logs and there are no problems, but there is no mention of me trying to contact the server to add the machine.

The only other thing I got wrong in my first email is the router that I'm using for my DHCP is also being used to look after the DNS.

I can succesfully ping the server name from the vista machine and I can map a drive to the server from the vista machine using the server name.

Finally sorted it,

The problem was becuase my router was looking after my dns.
I set the server up to manage dns and it works.
How ever still leaves the question why did it work no problems with xp pro, but not with vista.

insidesolutions_64U wrote:
> Finally sorted it,
>
> The problem was becuase my router was looking after my dns.
> I set the server up to manage dns and it works.
> How ever still leaves the question why did it work no problems with xp
> pro, but not with vista.
>
>

It doesn't really matter why. If you have a domain and the router was
doing DNS, you have DNS set up incorrectly anyway. The server should
only look to itself for DNS with forward/reverse lookup zones set for
the outside nameservers. Each workstation should only look to the server
for DNS.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Yes I know its a bit of a wierd situation, however the reason behind it was that the domain is a test domain in my home, which consists of one 2003 server, one xp box, one vista, but I also have a work laptop which is on a different domain.
Also due to being so noisy my girlfriend does not like me always leaving the server on, so thought might as well let the ADSL router take care of DHCP and dns, that way I only need the server on when I want to play around with the domain.

Ive had to settle using the 1st dns to the Server and the 2nd DNS to the router, but it still leaves with the problem that when I get to work with my laptop I have to change the Dns setting, shame there is not a third DNS available.

Suppose I could make the router DNS IP the same as my DNS at work then that should sort it out.

Not sure if that makes any sense to anyone, but ideas welcome?