This error is nothing to do with the Cisco setup or the configuration, well kind of. Its actually down to the packet size of the data on the network. You need to reduce the size of your MTU (Maximum Transmission Unit).
Quickest way is to start a Windows Command Prompt from Start > Programs > Accessories (in Win 7). Make sure you right-click and use Run As Admin.
Then type
netsh interface ipv4 set subinterface "Local Area Connection" mtu=1300 store=persistent
or use "Wireless Connection" if appropriate.
You can also type
netsh interface ipv4 show subinterfaces
to get a list of interfaces.
Or download a utility to do the job for you, c/o Cisco
http://sslvpn.emc.com/docs/setMTU.exe
Could be worth experimenting a bit to find what is the most appropriater MTU, using a higher value of 1400 might give slightly better performance.
Saturday, 18 July 2015
Wednesday, 1 July 2015
WindowsUpdate error 0x8007277a, MSE not updating either
Had a laptop that stopped loading Windows Updates following a spyware infection and subsequent clean-up by MBAM. Internet access was ok.
Eventually tracked the fix down to a winsock reset ...
Look in Start > Accessories and find Command Prompt
Right-click and Run As Admin
Then type ...
netsh winsock reset
netsh int ipv4 reset
You should get a prompt to restart the computer. We didn't need to, restarting the Windows Update service was sufficient to get everything working again (Start > Control Panel > Admin Tools > Services)
[Just as an aside, we had already run the Microsoft Windows Update Fixit tool and renamed the SoftwareDistribution folder - just in case the above netsh commands don't work on their own]
Eventually tracked the fix down to a winsock reset ...
Look in Start > Accessories and find Command Prompt
Right-click and Run As Admin
Then type ...
netsh winsock reset
netsh int ipv4 reset
You should get a prompt to restart the computer. We didn't need to, restarting the Windows Update service was sufficient to get everything working again (Start > Control Panel > Admin Tools > Services)
[Just as an aside, we had already run the Microsoft Windows Update Fixit tool and renamed the SoftwareDistribution folder - just in case the above netsh commands don't work on their own]
Subscribe to:
Posts (Atom)