• Embed Doc
  • Copy Link
  • Readcast
  • Collections
  • CommentGo Back
Download
 
 
Windows Vista Troubleshooting
يب سكلا قشع تحورـــــش
[ Xplover ]
 
esku86@msn.com
1
 
Windows Vista Network Troubleshooting
The networking problems discussed here are based on the assumption that you have a network that isworking fine, but adding a Windows Vista computer to the network creates problems connecting thisVista 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 WindowsVista 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 yourcomputers.There are many people complaining about Windows Vista networking. One particular problem involvesconnectivity problems between Vista and previous Windows versions (mostly XP) when they are on thesame network. You might be able to connect to another computer just fine, but as soon as you try tocopy a file, you run into trouble. You typically receive an error message that you don't have permissionto copy the file.Microsoft has acknowledged (see Microsoft Knowledge BaseArticle 932134)that Windows Vista may not function correctly with "outdated routers". Microsoft has released an InternetConnectivity Evaluation tool to test your router's compatibility.The very first thing you should do when having connectionproblems with Vista on your network is to check for updated driversfor your network card on the manufacturer's Web site. Also check for the latest firmware version of your router.If you run the Internet Connectivity Evaluation tool, and it showsthat your router does not support "TCP Extensions for HighPerformance", you can either change your router, or switch off thefeature in Vista. To do this, you'll have to open an elevatedcommand prompt:Click Vista's Start button, and in the
Start Search
box type
cmd
. Atthe top of the Start menu (under the
Programs
header), you will see
cmd.exe
listed; right-click this entry, and from the context menuclick 
Run as administrator
(
Figure
 
)(you can also press the
Ctrl+Shift+Enter
keys simultaneously after you typed
cmd
inVista's
Start Search
box, this will also get you an elevation prompt
Receive Window Auto-Tuning
 Vista has a new feature called
Receive Window Auto-Tuning
.This continually determines theoptimal receive window size bymeasuring the bandwidth-delayproduct and the applicationretrieve rate, and adjusts themaximum receive window sizebased on changing network conditions.Receive Window Auto-Tuningenables TCP window scaling bydefault, allowing up to a 16 MBwindow size. As the data flowsover the connection, Vista'sTCP/IP stack monitors theconnection, measures the currentbandwidth-delay product for theconnection and the application
 
 
Windows Vista Troubleshooting
يب سكلا قشع تحورـــــش
[ Xplover ]
 
esku86@msn.com
2
to run cmd.exe in administrator mode). At the command prompt,type
netsh interface tcp set global autotuninglevel=disabled
. Youshould get a response
Ok
. To check, you can run the command
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 thiscommand:
netsh interface tcp set global autotuningl=normal
 receive rate, and adjusts thereceive window size to optimizethroughput.
Problems connecting to the network
 If you have a DHCP server configured on your network, and your network is working fine withWindows XP, but your Windows Vista system cannot seem to get connected to your network (it will notreceive an IP address from the DHCP server), it could be that your DHCP server (which is usually arouter in a typical home network) does not support the
DHCP BROADCAST
flag. In Windows XPSP2, the BROADCAST flag in DHCP discovery packets is set to 0 (disabled). In Windows Vista, theBROADCAST flag in DHCP discovery packets is not disabled. This causes some routers (and somenon-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 serveris that your computer's IP address will be listed in the 169.254.x.x address range (a so called APIPAaddress). You can check the IP address of your computer by checking the status of your connection fromVista'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 theincompatibility of your DHCP server, but it's another thing to troubleshoot. This registry edit willdisable the DHCP BROADCAST flag in Windows Vista:
1.
 
Start the 
Registry Editor
 2.
 
Find & select
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ Tcpip \ Parameters \Interfaces \ {#####}
 You'll have to select the {#####} subkey that corresponds to the network adapter that is connected tothe network.3.
 
On the
Edit
menu, point to
New
, and then click
DWORD (32-bit) Value
 4.
 
Give the new entry the name
DhcpConnEnableBcastFlagToggle
 5.
 
Right-click
DhcpConnEnableBcastFlagToggle
, and then click
Modify
 6.
 
In the
Value data
box, type
1
, and then click
OK
 7.
 
Close the Registry Editor
Another issue that has been identified & fixed is that your Vista based computer will lose the defaultgateway settings when you wake it from sleep. Microsoft issued a fix for this issue back in September2007. See Microsoft Knowledge Base Article 933872. 
 
 
Windows Vista Troubleshooting
يب سكلا قشع تحورـــــش
[ Xplover ]
 
esku86@msn.com
3
Problems using a wireless connection
 There have been several problems identified, and Microsoft has issued fixes for these back in September2007 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 isselected in a user interface may be incorrect
 
A wireless profile that an independent hardware vendor (IHV) provides may be corrupted after you usethe wireless profile user interface to edit the profile. When this problem occurs, you may receive anerror message that Windows Explorer has crashed
 
Every time that you roam to a different wireless access point, you are prompted to provide a usercredential. 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 mayreject the authentication, and the IAS server may send an error message that the authentication hasfailed. 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 listedabove, 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 onto 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 shouldimprove the stability of wireless network services. For more information & download of this update, seeMicrosoft Knowledge Base Article 941649. 
Stateful Packet Inspection
 One of the problems is that Windows Vista's new TCP/IP stack falls apart when it encounters StatefulPacket Inspection (SPI) firewalls on some older routers. One option is to disable SPI in your router (notpossible in all routers), although this will weaken your network security. The first thing you should tryto do is to get updated firmware for your router from the router manufacturer's Web site.
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...