Ipv6 And Windows Networking

[tvadakia]

Does anyone have any links to any resources on how to get the developer version of IPv6 in Windows XP to work in a workgroup for filesharing? Is it possible? Do I need third party software to use it? How is it routed? What all do I need to know?

Thx to anyone with real answers or links to real answers.

-MT

[[idkfa]]

in SP1 it's includet, just use the normal Add Protocol Button ;)

i couldn't get it to work properly, but it's still "developer edition", so it's not meant for productive use.

[yashiro]

Welcome to Neowin. To make your stay a pleasant one you might want to try searching the internet first.

Then come back here with a specific problem.

Microsoft articles on IPv6

Google says...

How to Install IPv6

Click Start, click Control Panel, and then double-click Network Connections.

Right-click any local area connection, and then click Properties.

Click Install.

Click Protocol, and then click Add.

Click Microsoft TCP/IP version 6, and then click OK.

Click Close to save changes to your network connection.

[tvadakia]

Thanx for the welcome; however, I wan't asking how to install the protocol. That was a piece of cake. Getting two Windows machines to use the protocol for file sharing is much different. And even Google has nothing to say about that.

However, Google was kind enought to provide a spacific IPv6 Forum (although it has a $2000 US membership fee... yay!). Thank you.

~MT

[yashiro]

Once installed on all machines it will be used by default wont it?

I'm sure it's supposed to be transparent. Your not supposed to go - send file to \\mynetwork\station2 using IPv6 and not IPv4.

It's an interesting topic but the problem is you need a few networked PC's to play with it. A luxury some of us don't have.

Best of luck with your research anyway.

[tvadakia]

Well, thing is is I don't bind IPv4 to "Client for Microsoft Networks" or "File and Printer Sharing for Microsoft Networks" on "Ethernet Adapter #1" (my lan), but I do bind IPv6 to the service and client. Then I go ahead for "Ethernet Adapter #2" (external internet) and don't allow that adapter to use IPv6, but IPv4 is free to reign (except that it's still not bound to the service and client mentioned above.

I guess the best way of explaining it is like this:

Ethernet Adapter #1: (lan, no internal IPv4)

_X_ Client for Microsoft Networks

_X_ File and Printer Sharing for Microsoft Networks

_X_ QoS Packet Scheduler (default for Windows XP but not .NET)

_X_ IPv6

___ Internet Protocol (TCP/IP)

Ethernet Adapter #2: (internet, no external IPv6)

___ Client for Microsoft Networks

___ File and Printer Sharing for Microsoft Networks

_X_ QoS Packet Scheduler (default for Windows XP but not .NET)

___ IPv6

_X_ Internet Protocol (TCP/IP)

I have all my computers set up that way. Each of the #1 adapters going to a switch and each of the #2 adapters going to a router. It works well with NetBEUI (and it's a secure way of having an exposed network), but I was trying to get it to work with IPv6. I don't know much about the spacifics of addressing or transport of IPv6, and I was hoping to find someone that could help. This isn't a dire need type of thing, it's just experimentation.

Thanx

~MT

[Hyori]

START -> RUN -> cmd

ipv6 install

[Silverado Nomads]

Well In day to day use you wont make use of IPv6. like Tvadakia said there are forums for IPv6, and a IPv6 network(but you wont be surfing the internet with it, you'll only whats on the IPv6 backbone servers) whare you can use that protocol. But Todays Nodes, and servers still use the IPv4 Protocol.

As far as local networking, it's dependant on the OS. With enough tinkering you could get it set up on a type of "local" Network, whare your adapter goes through that protocol.

I've been reading up on it myself, it sounds pretty nifty but isn't ready for the masses yet(since they are still testing it.).