Re: WinXP doesn't pick up the hostname from DHCP

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Marc Reynolds [MSFT] (marcrey_at_online.microsoft.com)
Date: 02/27/04 

Date: Thu, 26 Feb 2004 19:45:58 -0600

Not sure what you mean by "doesn't pick up the hostname"??

nslookup will append the client domain suffix unless you give it a FQDN.
This is the design of nslookup. 

-- 
Thanks,
Marc Reynolds
Microsoft Technical Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karthik S S" <anonymous@discussions.microsoft.com> wrote in message
news:C96BD380-89D0-4DC4-8E84-00657E66A6CB@microsoft.com...
> Hi,
>
> We have DNS and DHCP servers configured in our network (no WINS Server).
>
> We have noticed that windows XP doesn't pick up the hostname from the DNS.
It picks up the IP, DNS Domain but not the hostname. We are not having this
problem with Windows 2000. Have any of you experience this problem?
>
> Also when we ping any hostname in the network it is successful but using
nslookup hostnames are not getting resolved unless otherwise we give FQHN.
Reverse lookup is just fine. (again these problems are only with Windows
XP). However it is picking up the "Connection-specific DNS Suffix" from the
DHCP. It is strange that nslookup doesn't work while ping is working.
>
> Is it a known issue?? Pl. help.
>
> Thanks,
> Karthik S S
>
>

Relevant Pages

  • Re: can access IPs but not by hostname
    ... I know you said nslookup shows DNS is fine but, can you you ping a host name ... Using any browser by hostname fails with server can't be found. ...
    (microsoft.public.windows.server.general)
  • Re: X window woes
    ... see if it shows an IP address, or an error message. ... in place of nslookup, but nslookup produces a cleaner output.) ... Your hostname needs to be resolvable on the local machine. ... The reason X needs to be able to resolve ...
    (Fedora)
  • RE: sshd/mysql errors.
    ... nslookup maxim.net gives 192.168.48.66 ... Adding a firewall deny rule for will 192.168.48.66 stop all traffic ... and how to get an ip of unkown hostname, as you knowm i should add ... Good chance attack packets are spoofed. ...
    (freebsd-questions)
  • Identifying which process is sending specific packets?
    ... Using netstat I have identified to suspect sites but nslookup does not ... reveal a hostname. ...
    (microsoft.public.win2000.security)
  • Re: hostname bogosity
    ... On Sun, 2003-12-14 at 03:10, John Smith wrote: ... Can't use nslookup because these are not public ...
    (Debian-User)