What is 192.168.1.1? Is it a router. It shows up as the gateway in all the
results but as a DNS server in only one result.
--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca
"Ecopoxy" <Ecopoxy@discussions.microsoft.com> wrote in message
news:0CF45E39-C84F-426C-B3E4-E6AA830D1341@microsoft.com...
> Kerry,
> The .10 machine was the old DC that died a few weeks ago. Before it died
> we
> promoted .9 to a DC and replicated AD etc. The DNS records for .10 were
> still in .9's DNS. I cleared all reference to .10 after I saw the above
> result in case it was causing the problem, but alas no it wasn't.
>
> I will send the XP info when I am back in the office tomorrow.
>
> In the meantime, I am going to install a virtual copy of Vista on my
> laptop
> at home and try to connect to the SBS2003 Premium AD Domain I have running
> at
> home. Will advise how this goes.
>
> "Kerry Brown" wrote:
>
>> I can't see anything obviously wrong there. I have a question though. Why
>> the two different results for pm06-p3server? In the first results you
>> have
>> two DNS servers 192,168.1.10 and 192.168.1.9 In the second results it
>> shows
>> 192.168.1.9 and 192.168.1.1. Can you post ipconfig /all from a working XP
>> workstation?
>>
>> --
>> Kerry Brown
>> Microsoft MVP - Shell/User
>> http://www.vistahelp.ca
>>
>>
>> "Ecopoxy" <Ecopoxy@discussions.microsoft.com> wrote in message
>> news:870CBAD5-F0E5-42BE-B363-E412CCE3EED8@microsoft.com...
>> > This is the Vista Box...
>> >
>> > Windows IP Configuration
>> >
>> > Host Name . . . . . . . . . . . . : PM01-P4ManDir
>> > Primary Dns Suffix . . . . . . . :
>> > Node Type . . . . . . . . . . . . : Hybrid
>> > IP Routing Enabled. . . . . . . . : No
>> > WINS Proxy Enabled. . . . . . . . : No
>> >
>> > Ethernet adapter Local Area Connection:
>> >
>> > Connection-specific DNS Suffix . :
>> > Description . . . . . . . . . . . : Realtek RTL8169/8110 Family PCI
>> > Gigabit E
>> > thernet NIC (NDIS 6.0)
>> > Physical Address. . . . . . . . . : 00-E0-4C-1C-01-35
>> > DHCP Enabled. . . . . . . . . . . : Yes
>> > Autoconfiguration Enabled . . . . : Yes
>> > IPv4 Address. . . . . . . . . . . : 192.168.1.13(Preferred)
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Lease Obtained. . . . . . . . . . : Thursday, 22 February 2007
>> > 10:13:04
>> > AM
>> > Lease Expires . . . . . . . . . . : Thursday, 22 February 2007
>> > 4:21:34
>> > PM
>> > Default Gateway . . . . . . . . . : 192.168.1.1
>> > DHCP Server . . . . . . . . . . . : 192.168.1.9
>> > DNS Servers . . . . . . . . . . . : 192.168.1.9
>> > NetBIOS over Tcpip. . . . . . . . : Enabled
>> >
>> > Tunnel adapter Local Area Connection* 6:
>> >
>> > Connection-specific DNS Suffix . :
>> > Description . . . . . . . . . . . :
>> > isatap.{120B1D6A-F4BE-445B-BD40-E81D709FA
>> > 5A2}
>> > 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.13%9(Preferred)
>> > Default Gateway . . . . . . . . . :
>> > DNS Servers . . . . . . . . . . . : 192.168.1.9
>> > NetBIOS over Tcpip. . . . . . . . : Disabled
>> >
>> > Tunnel adapter Local Area Connection* 7:
>> >
>> > Media State . . . . . . . . . . . : Media disconnected
>> > Connection-specific DNS Suffix . :
>> > Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
>> > Physical Address. . . . . . . . . : 02-00-54-55-4E-01
>> > DHCP Enabled. . . . . . . . . . . : No
>> > Autoconfiguration Enabled . . . . : Yes
>> >
>> >
>> > This is the DC...
>> >
>> > Windows IP Configuration
>> >
>> > Host Name . . . . . . . . . . . . : pm06-p3server
>> > Primary Dns Suffix . . . . . . . : hq.illawarra.01
>> > Node Type . . . . . . . . . . . . : Unknown
>> > IP Routing Enabled. . . . . . . . : No
>> > WINS Proxy Enabled. . . . . . . . : No
>> > DNS Suffix Search List. . . . . . : hq.illawarra.01
>> > illawarra.01
>> >
>> > Ethernet adapter LAN 1:
>> >
>> > Connection-specific DNS Suffix . :
>> > Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
>> > Adapter (1
>> > 0/100)
>> > Physical Address. . . . . . . . . : 00-B0-D0-68-5B-C4
>> > DHCP Enabled. . . . . . . . . . . : No
>> > IP Address. . . . . . . . . . . . : 192.168.1.9
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Default Gateway . . . . . . . . . : 192.168.1.1
>> > DNS Servers . . . . . . . . . . . : 192.168.1.10
>> > 192.168.1.9
>> >
>> > C:\Documents and Settings\Administrator.HQIC01>ipconfig /all
>> >
>> > Windows IP Configuration
>> >
>> > Host Name . . . . . . . . . . . . : pm06-p3server
>> > Primary Dns Suffix . . . . . . . : hq.illawarra.01
>> > Node Type . . . . . . . . . . . . : Unknown
>> > IP Routing Enabled. . . . . . . . : No
>> > WINS Proxy Enabled. . . . . . . . : No
>> > DNS Suffix Search List. . . . . . : hq.illawarra.01
>> > illawarra.01
>> >
>> > Ethernet adapter LAN 1:
>> >
>> > Connection-specific DNS Suffix . :
>> > Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
>> > Adapter (1
>> > 0/100)
>> > Physical Address. . . . . . . . . : 00-B0-D0-68-5B-C4
>> > DHCP Enabled. . . . . . . . . . . : No
>> > IP Address. . . . . . . . . . . . : 192.168.1.9
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Default Gateway . . . . . . . . . : 192.168.1.1
>> > DNS Servers . . . . . . . . . . . : 192.168.1.9
>> > 192.168.1.1
>> >
>> > "Kerry Brown" wrote:
>> >
>> >> Post the results of ipconfig /all from the Vista pc and from a DC with
>> >> DNS
>> >> running on it.
>> >>
>> >> --
>> >> Kerry Brown
>> >> Microsoft MVP - Shell/User
>> >> http://www.vistahelp.ca
>> >>
>> >>
>> >> "Ecopoxy" <Ecopoxy@discussions.microsoft.com> wrote in message
>> >> news:A63E5714-B829-48B7-9449-7B8EFC3C7AFE@microsoft.com...
>> >> > We have a WIN2K3 AD Domain running great with XP Pro clients. We
>> >> > have
>> >> > just
>> >> > performed a clean install of Vista Business onto a machine to
>> >> > evaluate
>> >> > before
>> >> > deployment.
>> >> >
>> >> > When we try to join the Vista machine to the domain we get an error
>> >> > stating
>> >> > that an Active Directory Domain Controller can not be contacted. An
>> >> > nslookup
>> >> > query from the Vista machine for the domain returns the correct ip
>> >> > address
>> >> > for the DC.
>> >> >
>> >> > What is interesting to note is that the Vista machine see's the
>> >> > other
>> >> > domain
>> >> > computers, but interprets them as bing in a workgroup with the same
>> >> > name
>> >> > as
>> >> > the domain.
>> >> >
>> >> > IPv6 has been disabled and Netbios over TCP/IP is enabled. ISA
>> >> > server
>> >> > has
>> >> > been shutdown and Vista firewall disabled.
>> >> >
>> >> > Any suggestions welcome...
>> >>
>> >>
>>
>>