Windows Vista Network Troubleshooting
Windows Vista Network Troubleshooting
Windows Vista Network Troubleshooting
The networking problems discussed here are based on the assumption that you have a network that is
working fine, but adding a Windows Vista computer to the network creates problems connecting this
Vista computer to your network.
First, take some time to read through this Microsoft TechNet article that describes File and Printer
Sharing in Windows Vista. One of the differences between Windows XP and Vista is that Windows
Vista by default does not allow simple file sharing. Access to shared folders, including the public folder
(if shared), requires a user name and password, so I suggest using usernames and passwords on all your
computers.
There are many people complaining about Windows Vista networking. One particular problem involves
connectivity problems between Vista and previous Windows versions (mostly XP) when they are on the
same network. You might be able to connect to another computer just fine, but as soon as you try to
copy a file, you run into trouble. You typically receive an error message that you don't have permission
to copy the file.
Microsoft has acknowledged (see Microsoft Knowledge Base Receive Window Auto-Tuning
Article 932134) that Windows Vista may not function correctly
with "outdated routers". Microsoft has released an Internet Vista has a new feature called
Connectivity Evaluation tool to test your router's compatibility. Receive Window Auto-Tuning.
This continually determines the
The very first thing you should do when having connection optimal receive window size by
problems with Vista on your network is to check for updated drivers measuring the bandwidth-delay
for your network card on the manufacturer's Web site. Also check product and the application
for the latest firmware version of your router. retrieve rate, and adjusts the
maximum receive window size
If you run the Internet Connectivity Evaluation tool, and it shows based on changing network
that your router does not support "TCP Extensions for High conditions.
Performance", you can either change your router, or switch off the
feature in Vista. To do this, you'll have to open an elevated Receive Window Auto-Tuning
command prompt: enables TCP window scaling by
default, allowing up to a 16 MB
Click Vista's Start button, and in the Start Search box type cmd. At window size. As the data flows
the top of the Start menu (under the Programs header), you will see over the connection, Vista's
cmd.exe listed; right-click this entry, and from the context menu TCP/IP stack monitors the
click Run as administrator (Figure) (you can also press the connection, measures the current
Ctrl+Shift+Enter keys simultaneously after you typed cmd in bandwidth-delay product for the
Vista's Start Search box, this will also get you an elevation prompt connection and the application
esku86@msn.com 1
Windows Vista Troubleshooting
to run cmd.exe in administrator mode). At the command prompt, receive rate, and adjusts the
type netsh interface tcp set global autotuninglevel=disabled. You receive window size to optimize
should get a response Ok. To check, you can run the command throughput.
netsh interface tcp show global. Look for Receive Window Auto-
Tuning Level: Disabled (Figure).
To set the TCP/IP Auto-Tuning Level back to Vista default, use this
command: netsh interface tcp set global autotuningl=normal
If you have a DHCP server configured on your network, and your network is working fine with
Windows XP, but your Windows Vista system cannot seem to get connected to your network (it will not
receive an IP address from the DHCP server), it could be that your DHCP server (which is usually a
router in a typical home network) does not support the DHCP BROADCAST flag. In Windows XP
SP2, the BROADCAST flag in DHCP discovery packets is set to 0 (disabled). In Windows Vista, the
BROADCAST flag in DHCP discovery packets is not disabled. This causes some routers (and some
non-Microsoft DHCP servers) to fail processing DHCP discovery packets.
One of the symptoms you can use to identify the failure of receiving an IP address from a DHCP server
is that your computer's IP address will be listed in the 169.254.x.x address range (a so called APIPA
address). You can check the IP address of your computer by checking the status of your connection from
Vista's Network and Sharing Center, or by running the command ipconfig /all from a command prompt.
It may not be true in all cases that the failure to obtain a correct IP address is caused by the
incompatibility of your DHCP server, but it's another thing to troubleshoot. This registry edit will
disable the DHCP BROADCAST flag in Windows Vista:
Another issue that has been identified & fixed is that your Vista based computer will lose the default
gateway settings when you wake it from sleep. Microsoft issued a fix for this issue back in September
2007. See Microsoft Knowledge Base Article 933872.
esku86@msn.com 2
Windows Vista Troubleshooting
There have been several problems identified, and Microsoft has issued fixes for these back in September
2007 as indicated in Microsoft Knowledge Base Article 932063:
IEEE 802.1X authentication that is based on Virtual Local Area Network (VLAN) switching may fail
In a wireless profile, the information about the Extensible Authentication Protocol (EAP) method that is
selected in a user interface may be incorrect
A wireless profile that an independent hardware vendor (IHV) provides may be corrupted after you use
the wireless profile user interface to edit the profile. When this problem occurs, you may receive an
error message that Windows Explorer has crashed
Every time that you roam to a different wireless access point, you are prompted to provide a user
credential. This problem occurs even if you have saved the user credential
You registered a Protected Extensible Authentication Protocol (PEAP) method that the IHV provided.
When you try to authenticate against an Internet Authentication Service (IAS) server, the server may
reject the authentication, and the IAS server may send an error message that the authentication has
failed. The Onex.dll file crashes when this problem occurs
The hotfix for these issues is not yet publicly available. If you experience any of the problems listed
above, go to this Microsoft Web page and enter the KB Article number (932063) and other requested
details, and Microsoft will send you the hotfix via email (it can take several hours for the fix to arrive).
Microsoft also has a fix available for another issue, described as follows: Five minutes after you log on
to a Windows Vista-based computer, 802.1X network authentication times out, and authentication fails.
Therefore, network connectivity is not established. You are not prompted to log on to a wired 802.1X
network during the five-minute period after you log on. For more information & the location of the fix,
see Microsoft Knowledge Base Article 937123.
In October Microsoft also released a compatibility, reliability and stability update, which also should
improve the stability of wireless network services. For more information & download of this update, see
Microsoft Knowledge Base Article 941649.
One of the problems is that Windows Vista's new TCP/IP stack falls apart when it encounters Stateful
Packet Inspection (SPI) firewalls on some older routers. One option is to disable SPI in your router (not
possible in all routers), although this will weaken your network security. The first thing you should try
to do is to get updated firmware for your router from the router manufacturer's Web site.
esku86@msn.com 3
Windows Vista Troubleshooting
IPv4 checksum
There are also reports that some network drivers are not setting the IPv4 checksum (you can verify this
with a network monitoring tool), and that switching off IPv4 Checksum Offload from the network
adapter's Advanced settings will fix connectivity issues. You can get to the network adapter's Advanced
settings by opening Device Manager from Vista's System control panel applet, and double-clicking
your network adapter under Network adapters. From your adapter's properties page, select the
Advanced tab and select IPv4 Checksum Offload under Property (Figure). Set the Value to
Disabled. Some people also suggest disabling TCP Checksum Offload (IPv4) & UDP Checksum
Offload (IPv4).
Please note that it may be possible that you can't set these options in your network adapter's properties.
This is a function of the adapter's driver. So as with most suggestions in this article, your 1st option
would be to make sure you are running the latest driver available for your network adapter!
Anti-Virus software
There have been quite a number of reports from users with Norton and McAffee software that their
Internet connection failed after an update. If you have either software, disable it and see if that restores
your Internet connection. If so, you may want to choose another AV software. For recommendations,
see this post on WindowsBBS.com.
Microsoft has a Knowledge Base Article that describes advanced troubleshooting for network adapters.
This article may give you some adittional information when troubleshooting connection problems. See
Microsoft Knowledge Base Article 325487.
Still Problems?
esku86@msn.com 4
Windows Vista Troubleshooting
Feel free to post a message on our WindowsBBS.com Support forum's Networking forum.
esku86@msn.com 5
Windows Vista Troubleshooting
esku86@msn.com 6
Windows Vista Troubleshooting
934430 - Network connectivity may fail when you try to use Windows Vista behind a firewall
device
934539 - Error message when a system service on a Windows Vista-based computer connects
to a system service on another Windows Vista-based computer: "cannot connect to
machine"
934555 - The Wireless Network tile is not displayed in Windows Mobility Center on a mobile
PC that is running Windows Vista
935222 - You cannot connect to a wireless network on a Windows Vista-based computer
935260 - Network Map is not displayed correctly in Windows Vista when you use DBCS
characters in the SSID for the network name
935279 - 802.11g is displayed instead of 802.11n for the wireless network adapter in Windows
Vista
935427 - When you transfer a file between a Windows Vista-based client computer and a file
server, Windows Vista stops responding
935755 - You cannot access a shared network resource that is hosted by a Windows Vista-
based computer if the SMB request packet exceeds the MTU size
936211 - How to troubleshoot network connectivity problems in Internet Explorer
937097 - Problems with the network, hard disk drive, or storage drivers cause a program to
stop unexpectedly in Windows Vista
937123 - You are not prompted to log on to a wired 802.1X network in Windows Vista
937151 - You cannot connect to the Internet from a Windows Vista-based computer that uses a
local .pac file
937168 - After you configure Internet Connection Sharing in Windows Vista, the network
connection stops working after one-to-two hours
937477 - After you wake a Windows Vista-based computer from sleep or from hibernation, the
network icon in the notification area does not show the correct connectivity status
937624 - After you turn on User Account Control in Windows Vista, programs may be unable
to access some network locations
938000 - FIX: A network redirect driver may not work correctly in Windows Vista
938062 - A red "X" appears in the icon for a mapped network drive in Windows Vista, even
though you can successfully access the drive
938091 - After you resolve an offline files synchronization conflict by using the "Keep both
versions" option, the conflict occurs again on a Windows Vista-based computer
938106 - Error message when you synchronize files on a Windows Vista-based computer:
"Unexpected Network Error"
938475 - Error message when you use a Windows Vista-based computer to try to access files
on a Windows Vista-based file server: "<DriveLetter>:\ is not accessible. Insufficient
system resources exist to complete the API"
940291 - Error message when you try to install a program from the network on a Windows
Vista-based computer: "Fatal error during installation"
941145 - Unwanted wake-up events may occur when you enable the Wake On LAN feature in
Windows Vista
941542 - When you try to connect a Windows Vista-based computer to a network printer
whose name is not a UNC path, the connection fails
esku86@msn.com 7
Windows Vista Troubleshooting
941808 - After you lock and then unlock a Windows Vista-based client computer, you may be
prompted for user credentials before you can access network resources
942541 - After you use Windows Photo Gallery to display an image in full-screen mode on a
Windows Vista-based computer, the image is not displayed on a network projector
that is connected to the computer
943451 - You cannot access a network share on a Unisys MCP server from a Windows Vista-
based computer by typing a UNC path that does not include the share name
esku86@msn.com 8