Isatap and 6TO4 adapter problem in device manager
Welcome, Guest. Please login or register. Did you miss your activation email?
Britec Computer Tech Help Support Forums  « Microsoft Support  «  Windows Vista Support « Isatap and 6TO4 adapter problem in device manager
Pages: [1]
  Print  
Author Topic: Isatap and 6TO4 adapter problem in device manager  (Read 590 times)
quinnlaup
Jr. Member
**
Posts: 54


View Profile
« on: July 26, 2010, 02:09:55 PM »

Hi All,

Got a vista laptop in today that would not connect wirelessly looked at device manager and found issues with both the 6TO4 adapter and the isatap. Tried uninstalling and reinstalling the adapter also tried resetting tcp/ip protocol (using the netsh command) Azn but no luck. Was thinking of trying a repair install unless anyone else has some suggestions? All help gratefully accepted.

Regards

quinnlaup
Logged
Britec
Administrator
Hero Member
*****
Posts: 3346



View Profile
« Reply #1 on: July 26, 2010, 03:17:12 PM »

 Azn quinnlaup.

Many new Laptops come with a physical switch that disables the Wireless (helps to save battery power if the Wireless is not working)

Many new Wireless Laptops and Wireless ready Desktops come with a configuration that loads the Original Wireless manufacturer’s Utility at Startup.  The Wireless connection can be maintained only by one agent; as a result most of these utilities are programmed to switch Off Windows Zero Configuration (WZC). 

Many people prefer the flexibility of WZC.  In such a case the 3rd party Utility has to be disabled from starting, and WZC has to be initiated again.

Note: It is important that the Wireless should be managed only with one application.       
You can use the Original Utility, or WZC.  When one is used the other has to be Off 
(Not loaded into memory, and not maintained as active Windows service).

Try this:

Click Start and Run, in the Run Box type cmd and click OK.

At the prompt of the open Command Box type, ipconfig/flushdns

If every thing were OK, you would get the message,

Successfully flushed the DNS Resolver Cache.

In addition, the DNS cache is flushed as part of repairing the Network’s TCP/IP Stack

If instead of Successful Flushing you get the message indicated that, the DNS could be Flushed.

Take a look at Windows Services; make sure the DNS Client Service is running.

Also try this:

Disable Firewall, Antivirus, try another browser, and disable any wep security in router and make sure its set to DHCP and check TCP/IP setings make sure its set to DHCP and make sure no proxy server is setup. check wireless light is on.
Logged



quinnlaup
Jr. Member
**
Posts: 54


View Profile
« Reply #2 on: July 26, 2010, 05:16:41 PM »

@Britec

thanks for the reply not sure if its a clash between either WZC or something like intel pro wireless that is preventing the wireless from working. Ican sort that out as per your instructions however how can i resolve the isatp and 6to4 adapter issues in device manager?? do you think that they could be contributing to the connectivity issue. I have seen this problem before where they were the root cause had to reinstall o/s dont want to do that if possible!! Thanks for your prompt response

regards

quinnlaup
Logged
MrTicker
Sr. Member
****
Posts: 343



View Profile
« Reply #3 on: July 27, 2010, 02:02:16 AM »

Hi there,

In a nutshell, IPv6 (Internet Protocol version 6)is the Internet Protocol version which is designed to succeed IPv4,(Internet Protocol version 4) the protcol currently in use, when the address space provided by IPv4 runs out in the near future. You can read more here: http://en.wikipedia.org/wiki/IPv6.

The Microsoft ISATAP device (Inter Site Automatic Tunneling Address Protocol)the ISATAP adapter encapsulates IPv6 packets by using an IPv4 header.This functionality enables the client to transport IPv6 traffic over an IPv4 infrastructure. Read more info here: http://support.microsoft.com/kb/932520

You should not need to do a OS reinstall to resolve this issue and I don't think that it is factor contributing to your connectivity issue and the problem lies elsewhere, follow the steps below to see if this helps.

The 6to4 adapter is a component used for transmitting IPv6 packets trough IPv4 network correctly.

In some cases, there will be a code 31 or code 10 error appearing beside this component. A possible reason is, the network adapter doesn’t support this feature. Try updating the driver for your network adapter or chipset, and then try to uninstall and reinstall the this component. 

If this doesn’t solve the problem, your network adapter does not support this component. You can completely ignore this error if there isn’t IPv6 network deployed in the environment. The error won’t affect your system.

To remove the error message, right-click the Command Prompt>Run as Administrator, type>netsh in 6to4 set state disable, press Enter. The component will be disabled and hidden.

Cheers, HTH,

ticker
Logged

Britec
Administrator
Hero Member
*****
Posts: 3346



View Profile
« Reply #4 on: July 27, 2010, 02:37:27 AM »

Make sure your using IPv4 like Ticker said and also uninstall any 3rd party wireless software and use WZC (Wireless Zero Configuration)...But if you want to use the 3rd party software make sure WZC (Wireless Zero Configuration) is turned of in services.

You should not have to format computer for this type of problem.
Logged



MrTicker
Sr. Member
****
Posts: 343



View Profile
« Reply #5 on: July 27, 2010, 03:15:42 AM »

Hi again,

One other thing for you to check,

Go>Start>Network>Network Sharing Centre>Change Adapter Settings and right click your wireless adapter, Click>Properties and check to see if there is a tick alongside the Internet Protocol Version 6 (TCP/IPv6) entry, if so remove it.

Close all down and reboot and check that it is still unchecked. Doing this will not be detrimental to your system as you will not be using IPv6.

Cheers,HTH,

ticker
« Last Edit: July 27, 2010, 03:20:29 AM by MrTicker » Logged

Pages: [1]
  Print  
 
Jump to: