DNS problem via W2K3

[Perry Diels]

Hello,

I can ping and surf to IP based addresses, but I cannot get to named
addresses. I have disabled IPv6
functionality, tested with both dynamic and static IP address, setting DNS
servers to both my gateway (Windows 2003 server) and to my ISP's servers. I
have run out of ideas.

Any hints and tips on what to try next is appreciated.

 

[Johannes Mayr]

Dear Community

I have the same problem and already found some other posts regarding this
problem with RC1 and still with 5728,
unfortunately no solution so far.

The strange thing is that DNS lookups via nslookup work just fine - however,
the system is unable to resolve DNS names (ping, IE...)
However, I can ping when using the IP-address instead.

I wonder, why there is no feedback from someone@MS so far - this seems to be
an issue with RC1 upwards which has to be solved until RTW
Could it be the case that the local IP-range I am using is causing the
issue - my DHCP is configured to use 169.254.0.0/24

In order to investigate the issue I enabled packet logging in Vista's
firewall - DNS requests originated from nslookup appear in the log -
however, there is broad silence when trying e.g. ping www.microsoft.com or
ping atlantis(which is a local computer name resolvable via the local DNS).

Note that when checking the interface configuration via "ipconfig /all" all
attributes are retrieved correctly from the local DHCP


I am looking forward to get instructions on working around this problem
which hopefully will be solved for RTW,

Hannes.

 

[Perry Diels]

Helo Johannes,

Thanks for your input. What you describe is exactly the same problem I'm
involved with, in every detail also same thing for nslookup etc. ...

Our corporate network range is also 169.254.x.x more precisely 169.254.0.255
subnet mask 255.255.255.0
The w2k3 server is 169.254.0.104 which has routing and remote access
enabled.

I keep looking forward for a solution to his problem.

Best Regards,
Perry

 

[news.microsoft.com]

Hello Perry,

I did some further investigations on this issue. Trying e.g. ping -4
www.microsoft.com works without problems whereas ping www.microsoft.com
simply fails. Based on this I completely disabled IPv6 (using the registry
setting) but the behavior still was the same - ping -4 works but not ping.

Then I added IPv6 to my W2k3 server and configured the DNS to allow queries
from IPv6 as well. Unfortunately Vista still showed the same behavior - I of
course verified IPv6 functionality by using nslookup which took the IPv6
address of my W2k3 server for connecting to DNS.

Finally I changed my IP subnet from 169.254.0.0/24 to 172.16.0.0/24 and
everything works as normal now - strange that Vista made such problems
whereas my XP and W2k worked just fine.

Strangely enough the change had also a positive effect when using my PDA to
connect via my AP - it failed in the past but after having changed the IP
segment it works fine (needless to say that my Notebook connected to the AP
without problems before having changed the IP as well)

Summarizing I can say that 169.254.0.0/16 is not a good choice for using via
DHCP as it seems to conflict with the automatic configuration scheme.


Best regards,
Hannes

 

[Perry Diels]

Hello Hannes,

Thanks for your answer and for further investigating this issue. Guess what,
I did somewhat the same test scenario's as you did the last few days/nights
and I acknowledge that I have quite the same results as you did. However I
changed it slightly a different way.

On our W2K3 server routing and remote access is typically enabled, mainly
because there's VPN functionality enabled. Note that the latter is not often
used and we can live some time without. What I did was totally disable
Routing and Remote Access and I have enabled the simple NAT as Internet
sharing method in W2K3. Now the network defaults to 192.168.0.0
(255.255.255.0), automatically Windows Vista got a correct IP address from
DHCP and everything was working perfectly, LAN and WAN without any problems.
And yes, the same goes for my PDA (Windows Mobile 2005), before I needed to
specify the 169.254.x.x address manually, now it's automatically assigned by
DHCP.

ULITMATEly we have both experienced quite the same behavior, can we agree
that Microsoft has to make improvements in that part of Windows Vista?

But there's more, today our network is up and running as expected,
everything works great apart from the Windows Vista machine! No LAN no WAN
nothing. It cannot get it's auto IP from the W2K3 server anymore. After a
while it get's an autoconfig local address. I have
repaired/renewed/restarted the machine ....nothing helps. Except when I
manually enter the IP4 IP address 192.168.0.x everything works again
(fortunately) ... but do you have any idea why it cannot get an automatic IP
address from DHCP, whereas all the other machines in our network do.

Strange stuff,

Best regards,
Perry