Cannot find Domain Controler

I have a new Vista Business notebook that cannot see the windows 2003 server
(DC) on the network. It DOES see all other XP machines and does get to the
internet.

I tried dynamic and static IPs on the notebook. And I have the DNS on the
notebook set to the server IP.

I can reach a server shared folder by IP i.e. \\192.168.0.250\public but
this does not seem to work to log on to the domain etc. And I cannot join the
domain as the Vista PC cannot see the server by name.

I would appreciate any ideas why or what is different with the Vista PC.

 

Is the date & time the same between DC and Vista (<5mn) ?

Do you use the FQDN name to join ?

 

I'll have to check the time and data issue. But I did use the FQDN to find
the server named (poweredge.buschthiem.local) also tried with out the local
and without the pwoeredge as the domain name is buschtiem.

How can I "search" for a computer (by name) on the network using Vista? I
could do the often in XP.

 

When you try to join AD, you must use buschthiem.local only.

 

Yes I tried it that way, said the server and or active directory could not be
found (bouschthiem.local), the strange thing is other XP machines can join
and logon to the domain.

 

Try adding the domain controller server as the primary DNS server in your
Vista IP configuration before trying to join the domain.

 

The IP of the primary Domain Controler is the ONLY IP in the Vista DNS
configuration

 

could you check time & date ?
Any eventlog error on the vista ?
Are you using a domain admin account or a one with deleated right ?

 

The Date is the same the time is 2 minutes off. Nothing in the event log
except a anti virus app comment.

The user of the Vista PC is a user on the domain. However when trying to
join the domain I use the administrator account

Here is a copy of the IP config from the Vista PC
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Ken Beutel>
C:\Users\Ken Beutel>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : KenBeutel-NB
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 590x 10/100 Ethernet
Physical Address. . . . . . . . . : 00-16-D4-DE-E0-FA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::4464:1825:fba3:5b58%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.238(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.250
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : wowway.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-1B-77-E2-A6-34
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.wowway.com
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 7:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{3AACE8A8-F7FA-4F76-A69F-8278F03B0
1F7}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.238%12(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.250
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Local Area Connection* 10:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4136:e390:180a:3322:3f57:fe11(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::180a:3322:3f57:fe11%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\Users\Ken Beutel>

 

what is this second dns server ?
DNS Servers . . . . . . . . . . . : 192.168.1.250

is this dns suffix ok ?
Connection-specific DNS Suffix . : wowway.com



--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr

 

It is the IP of the router that At&T put in

 

Why do you have the IP of your router as dns server ?

can you issue this from the vista:
nslookup www.google.com
nslookup myserver.wowway.com
(replace myserver by the name of your server)



--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr