Hi

We have a network with a broadband connection managed by a VIGOR 2820n router. We are having trouble with two recent VISTA machines. They appear to be unable to access the internet intermittently, whilst other machines running Linux Fedora and Windows XP are working fine.

Whilst other machines are working perfectly, we can ping the local IP of the router with good, consistent timings. At the same time, running in another command prompt on the same workstation, we can be trying to ping an external address (either site name or numeric IP). At the same time, another linux or XP workstation can be pinging everything successfully.

We have switched off the VISTA default of having IPV6stack active.

Does anyone know what might be causing this?

Thanks

Tayler

Out of interest is the Vista firewall on or off?
If on does it make any difference off?

Thanks for your reply. It doesn't make any difference whether it is on or off.

Tayler

I assume you've been googling for general Vista router problems - here is one hit http://www.reviewingit.com/index.php/content/view/29/2/

I think it will (from the other evidence) be Vista related rather than Draytek specific so generic answers may help.

I assume that the PCs are connected by wire to the router rather than wireless. If its wireless then its likely to be driver related as I had problems with Vista and wireless especially if its 64 bit vista.

Vista's networking is basically broken - they have implemented an 'auto-tuning' network stack which just seems to slow the network connection to a crawl.

The following will tell you how to disable this:


Running "netsh interface tcp set global autotuninglevel=disabled" at a command prompt turns the clearly BROKEN microsoft auto-tuning BS in the network stack OFF. I'm not sure what algorithm they use, but someone needs to convey to them that it's severely lacking and causing MAJOR issues. I now have to inform THOUSANDS of users that if they are running Vista, they need to have and administrator come to their PC and run this.


(This does not seem to be a problem in Windows 7, so it's either disabled by default or fixed.)