Re: Name resolution issues on W2K Pro
From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 06/04/04
- Next message: Jim Mapes: "Re: DNS fails external domain resolution"
- Previous message: Deji Akomolafe: "Re: W2K authority dns for more than one domain"
- In reply to: Rob Pagé: "Name resolution issues on W2K Pro"
- Next in thread: Rob Pag?: "Re: Name resolution issues on W2K Pro"
- Reply: Rob Pag?: "Re: Name resolution issues on W2K Pro"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Jun 2004 08:17:46 -0400
In news:101c072c.0406032026.28b4ce60@posting.google.com,
Rob Pagé <robpage01@hotmail.com> posted their thoughts, then I offered mine
> I have two workstations running Windows 2000 Pro behind a linksys
> firewall. Both worked great. Two days ago one of them started having
> problems. Workstation 1 can not resolve any names on the internet.
> As a result, e-mail hosted with ISP and web access is not working.
> This workstation also can not print to an IP printer on the internal
> network. I've been able to confirm that TCP/IP is working fine. I'm
> able to ping the router and the ISP's 2 DNS servers. I've also
> confirmed that the name resolution for items in the hosts file works
> fine. I had problems with netbios name resolution but a re-install of
> the windows client fixed this.
Which Windows client are you talking about here?
What sort of problems? What determination or article read suggested to
reinstall the WIndows client?
> If I run nslookup I get the following
> error: Can't find server name for address x.x.x.x. No response from
> server.
This above is NOT a client issue. THis is a DNS server issue, or rather lack
of a zone issue. That message is saying your DNS server listed in the IP
properties does NOT have reverse entry. So if you are usin your internal DNS
(which is recommended in AD) then I would suggest to create a Reverse zOne
for your subnet and make sure YOUR DNS server has a PTR entry created.
> However these servers work well from the second workstation.
> I've uninstalled TCP/IP and reinstalled. TCP/IP settings are hard
> coded on workstation. Client is not using DHCP anywhere. Workstation
> has Novell client and IPX installed as well but those services and
> protocals are working fine. This same workstation also can't print to
> the IP printer but the second one can print without any problems. I
> can ping the printer but not print to it. I'm thinking there is a
> problem with the TCP/IP protocal stack but not able to figure out
> where it is.
IF you remove the Novell client, does it work?
> It seems like a DNS problem but the printing problem
> does not use DNS and this confuses me.
I would have said the same thing. If connecting by IP, DNS is not even
involved.
> I've checked the services
> running on the workstation and DNS client service is running. I've
> also tried flushing the DNS cache on the workstation to no avail. Any
> assistance would be appriciated.
Is the DHCP client service running? That must be running in ALL
circumstances, DHCP or not. It's tied into the DNS client side resolver
service.
>
> Thanks in advance for your help.
-- Regards, Ace Please direct all replies to the newsgroup so all can benefit. This posting is provided "AS-IS" with no warranties and confers no rights. Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP Microsoft Windows MVP - Active Directory HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a pig. -- =================================
- Next message: Jim Mapes: "Re: DNS fails external domain resolution"
- Previous message: Deji Akomolafe: "Re: W2K authority dns for more than one domain"
- In reply to: Rob Pagé: "Name resolution issues on W2K Pro"
- Next in thread: Rob Pag?: "Re: Name resolution issues on W2K Pro"
- Reply: Rob Pag?: "Re: Name resolution issues on W2K Pro"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
