You can't join the domain or do any domain-related things unless your DNS
server is your local AD DNS server. All Windows services (even Netlogon) are
discovered via SRV records that only exist on the DNS server for the AD
Domain you are trying to join / log on to. If you cant' resolve Internet
addresses, your DNS server is not set up correctly. If you can't resolve
local addresses you're in even bigger trouble. But the first thing to do is
verify TCP/IP connectivity using IP addresses, taking DNS out of the
picture. If you don't have basic layer 3 connections, nothing else will
work.
....kurt
"billy" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> thanks for the reply kurt. windows firewall is off... i even tried
> temporarily turning the firewall on the router off to no avail. when i
> put the dns server as 192.168.1.5 on the tcp/ip properties on my xp
> machine it loses internet connectivity. also, when i do ns lookup from
> either machine, i get "can't find server name for address 192.168.1.5"
> the xp machine then goes to a comcast server as it's default and my
> server says "default: unknown/address: 192.168.1.5" and keeps internet
> connectivity. the router has spots for dns1, dns2, and dns3. i put
> 192.168.1.5 in one and leave the other two blank. still can't ping
> from the pc. thanks again and any other suggestions would be great.
>
|