M
Michaelk
Hi everyone,
This is probably basic for all you network wizard
Why does windows need the dot to resolve the name when the domainname
is empty?
(following the first label in the FQDN)
Check this example below:
C:\>nslookup dreambox
Server: dns
Address: 192.168.0.1
Name: dreambox
Address: 192.168.0.124
C:\>ping dreambox
Ping request could not find host dreambox. Please check the name and
try again.
C:\>ping dreambox.
Pinging dreambox [192.168.0.124] with 32 bytes of data:
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.0.124:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 90ms, Average = 23ms
Client is DHCP
Node type = Hybrid
Both the "Primary Dns Suffix" and the "Connection-specific DNS Suffix"
are empty
My linux hosts do not have this problem...
I there a way to turn this (annoying) feature of? All hosts are on my
internal home network so I don't really need a domain name...
Any other hints or clues?
Thanks in advance
Michael
This is probably basic for all you network wizard

Why does windows need the dot to resolve the name when the domainname
is empty?
(following the first label in the FQDN)
Check this example below:
C:\>nslookup dreambox
Server: dns
Address: 192.168.0.1
Name: dreambox
Address: 192.168.0.124
C:\>ping dreambox
Ping request could not find host dreambox. Please check the name and
try again.
C:\>ping dreambox.
Pinging dreambox [192.168.0.124] with 32 bytes of data:
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.0.124:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 90ms, Average = 23ms
Client is DHCP
Node type = Hybrid
Both the "Primary Dns Suffix" and the "Connection-specific DNS Suffix"
are empty
My linux hosts do not have this problem...
I there a way to turn this (annoying) feature of? All hosts are on my
internal home network so I don't really need a domain name...
Any other hints or clues?
Thanks in advance
Michael