DNS problem

[Perry Diels]

Hello,

This is the network scenario:

Vista RC1 ==> Windows 2003 server (standard SP1) ==> broadband cable modem.

Windows Server 2003 acts as gateway to the internet. This works perfectly
for all PC's (win XP) in our network, but Vista RC1 cannot access the
internet, unless an ip address is entered in IE. Same goes for a ping
request from the command prompt it works by IP address but not by name. If I
enter a DNS address manually in the IPv4 section of the network adapter, it
is still not working.

Has anyone got an idea how to solve this problem? It worked OK with a
previous Vista beta. RC1 has been installed from scratch. I have tried
disabling the Vista Firewell yet.

Thanks for your help,
Perry

 

[Guest]

Hi,

You can troubleshoot with "nslookup" command at the command prompt window.
Is Network Discovery Turned on ? How do you assign IP address, DHCP or
Manually ? If DHCP then check the DNS entries with ipconfig/all commad.

You can also enter the host mappings in the host file at
c:\Windows\System32\drivers\etc\hosts. Openwith notepad and enter the name
and ipaddresses resp. and save the file.

Just few things to try it out.

abc

 

[Perry Diels]

Hello abc,

Thanks for your tips:

nslookup works perfectly, it always points correctly the websites address.
When manually copying this in the browser the site shows up.
Network Discovery is ON. IP addresses are assigned by DHCP (also tried
manually)
With ipconfig/all the DNS server is correctly poinitng to 169.254.0.104 (our
W2K3 server) this is exactly as on our working XP machines.

Can I copy a hosts file from a working XP machine in the same network?
This being said, when I enter a site in hosts and the try t open it with IE
it says invalid name (http:///)

I don't get it, because nslookup works perfectly, hence the addresses can be
correclty resolved from that machine.

Any other idea?

Thanks again,
Perry

 

[Lloyd]

Hi,

Vista's TCP/IP stack has an ability to auto-tune the TCP/IP Window size - se
Windows Scaling.
Some routers and security appliances are not fully RFC 1323 compliant and
they cannot yet handle Vista's
stack.

Go to a command prompt and open it as an administrator,

Issue the following command and reboot your system, netsh int tcp global set
autotuninglevel=disabled

***Observe to ensure that the command shell returns an OK - to indicate the
command executed as desired.

****You may have to navigate to actually execute the command - e.g., to
netsh and then to interface and then
issue, the command.

*****Do contact your appliance and or router vendor and advise them of the
SPI limitation and compliance issue
ref RFC 1323.

Good Luck,

Lloyd

 

[Guest]

I just ran this command and I had to run it as :
netsh int tcp set global autotuninglevel=disabled

not

netsh int tcp global set autotuninglevel=disabled

Thanks for the great tip!

 

[Robert L [MVP - Networking]]

Thank you for the feedback.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I just ran this command and I had to run it as :
netsh int tcp set global autotuninglevel=disabled

not

netsh int tcp global set autotuninglevel=disabled

Thanks for the great tip!