"(From a JohnWill post)
TCP/IP stack repair options for use with Vista.
Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Reboot the machine.
----------------------------------------------------------------------------------------
From a Johnwill post
Check your Services are Started on all PCs:
COM+ Event System (for WZC issues)
Computer Browser
DHCP Client
DNS Client
Network Connections
Network Location Awareness
Remote Procedure Call (RPC)
Server
TCP/IP Netbios helper
Wireless Zero Configuration (XP wireless configurations only)
WLAN AutoConfig (Vista wireless configurations only)
Workstation
Note: You can check the services in Control Panel, Administrative Tools, Services.
All of these services should be started, and their startup type should be automatic (or perhaps manual)."
'via Blog this'
TCP/IP stack repair options for use with Vista.
Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Reboot the machine.
----------------------------------------------------------------------------------------
From a Johnwill post
Check your Services are Started on all PCs:
COM+ Event System (for WZC issues)
Computer Browser
DHCP Client
DNS Client
Network Connections
Network Location Awareness
Remote Procedure Call (RPC)
Server
TCP/IP Netbios helper
Wireless Zero Configuration (XP wireless configurations only)
WLAN AutoConfig (Vista wireless configurations only)
Workstation
Note: You can check the services in Control Panel, Administrative Tools, Services.
All of these services should be started, and their startup type should be automatic (or perhaps manual)."
'via Blog this'
unchecked "avg network driver filter" from lan properties and it started working fine
ReplyDeletejust couldn’t leave your website before telling you that we really enjoyed the quality information you offer to your visitors… Will be back often to check up on new posts.
ReplyDelete