Hurricane Electric's IPv6 Tunnel Broker Forums
September 10, 2010, 01:51:47 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to Hurricane Electric's Tunnelbroker.net forums!
 
   Home   Help Search Login Register  
Hurricane Electric's IPv6 Tunnel Broker Forums > General IPv6 Topics > IPv6 on Windows > Vista : duplicate name exists on the network
Pages: [1]
« previous next »
  Print  
Author Topic: Vista : duplicate name exists on the network  (Read 4429 times)
uzzi
Newbie
*
Posts: 2


View Profile
« on: May 12, 2009, 02:21:43 pm »
Hello,

I run Vista 64bit on my PC.  When I enter the command 'netsh interface ipv6 add v6v4tunnel IP6Tunnel 77.109.120.xx 216.66.80.26', I get the following errror message :
You were not connected because a duplicate name exists on the network.  If joining a domain, go to System in Control Panel to change the computer name and try again.  If joining a workgroup, choose another workgroup name

Does anyone know how to solve this problem ?  Thanks  a lot !
Logged
broquea
Administrator
Hero Member
*****
Posts: 789


text


View Profile WWW
« Reply #1 on: May 12, 2009, 02:47:43 pm »
Not sure, but since you are using Vista 64bit, make sure you use:

netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel $ipv4b $ipv4a

note the interface= addiition. This was a difference between 32bit and 64bit, that happens to work in 32bit as well.
Logged
uzzi
Newbie
*
Posts: 2


View Profile
« Reply #2 on: May 12, 2009, 02:59:45 pm »
I tried it, but still the same error message
Logged
dogers
Newbie
*
Posts: 2


View Profile
« Reply #3 on: August 14, 2009, 12:51:24 pm »
Did you ever get past this? I'm experiencing this at the moment, off and on..!
Logged
Bram
Newbie
*
Posts: 2


View Profile
« Reply #4 on: August 20, 2009, 01:28:54 pm »
Cmon admins, answer this question plz....

I'm stuck for 3weeks or more now.
Reinstalled windows 7 since RTM is available and still having this problem.

Can't get a connection so when I type this command again in cmd, I receive the error.
Tried everything and still no solution.


HE, Solve this....
Logged
dataless
Newbie
*
Posts: 23


View Profile
« Reply #5 on: August 20, 2009, 03:04:43 pm »
Aside from changing the IPs shown, here is the exact commands I used on Windows 7 x64 RC..

netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.2.100 216.66.22.2
netsh interface ipv6 add address IP6Tunnel 2001:470:x:xxx::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:x:xxx::1

Remember if you are behind an NAT router to use you private IP and not your public one, like shown above.
Logged
broquea
Administrator
Hero Member
*****
Posts: 789


text


View Profile WWW
« Reply #6 on: August 20, 2009, 05:03:57 pm »
Quote from: Bram on August 20, 2009, 01:28:54 pm
Cmon admins, answer this question plz....

I'm stuck for 3weeks or more now.
Reinstalled windows 7 since RTM is available and still having this problem.

Can't get a connection so when I type this command again in cmd, I receive the error.
Tried everything and still no solution.


HE, Solve this....

How would you like us to solve something remote, that we have no hands-on access to? I've run WinXP, Vista and now Win7 and never encountered this problem with the netsh commands. I don't have any magic tricks up my sleeves. I'm also stuck behind NAT on Comcast, and using my 10.x.x.x IPv4 address on the first netsh command works. If I can't replicate the problem, not sure how to come up with an answer.

Try this.... First, use netsh to delete the interface if it somehow still got created. Then, depending on the IPv4 address assigned to your LAN adapter, you'll want to use that IPv4 address. As the other poster on your thread mentions, if you are behind a NAT/Firewall appliance, you'll want to use that private IP address on the first netsh command. If the IPv4 address is what you are assigned by the ISP, then make sure you are doing everything as an Administrative account under Win7
Logged
Bram
Newbie
*
Posts: 2


View Profile
« Reply #7 on: August 22, 2009, 04:53:43 am »
Thankx guys,

I always used my public ip instead of my local ip.
I've read some manuals and they all used their public ip so I did the same.

So for the other people with this problem:

-First delete the interface you created (with the command netsh interface ipv6 add v6v4tunnel IP6Tunnel [public ip] 216.66.22.2):
netsh interface ipv6 delete interface IP6Tunnel

-and then start over again but use your local ip:
netsh interface ipv6 add v6v4tunnel IP6Tunnel [local ip] 216.66.22.2
Logged
dataless
Newbie
*
Posts: 23


View Profile
« Reply #8 on: August 23, 2009, 04:59:15 pm »
Glad you got it working Bram!

Sometimes it's down to just one little detail like that.  Smiley
Logged
milliamp
Newbie
*
Posts: 4


View Profile
« Reply #9 on: October 03, 2009, 08:51:30 pm »
Quote from: Bram on August 22, 2009, 04:53:43 am
Thankx guys,

I always used my public ip instead of my local ip.
I've read some manuals and they all used their public ip so I did the same.

So for the other people with this problem:

-First delete the interface you created (with the command netsh interface ipv6 add v6v4tunnel IP6Tunnel [public ip] 216.66.22.2):
netsh interface ipv6 delete interface IP6Tunnel

-and then start over again but use your local ip:
netsh interface ipv6 add v6v4tunnel IP6Tunnel [local ip] 216.66.22.2


I had exactly the same problem.

I read the guide that said:

NOTE* When behind a firewall appliance that passes protocol41, instead of using the IPv4 endpoint you provided to our broker, use the IPv4 address you get from your appliance's DHCP service.

I tried public first but figured I would check the forum for the netsh syntax to remove the incorrect tunnel. It worked, thank you.
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!