Re: ipv6 - dest net unreachable

From: Ron Lowe (ron-msng_at_{d.e.l.e.t.e.}lowe-family.me.uk)
Date: 12/19/04 

Date: Sun, 19 Dec 2004 19:21:39 -0000

"Betsy" <Betsy@discussions.microsoft.com> wrote in message
news:6807D116-E7B4-4B43-A18F-3CA9F8AF4657@microsoft.com...
> First (and again) let me express my appreciation for you help. I am
> anxiously
> waiting for the book you recommended to arrive and without your help I
> would
> not be making any progress at all.
>
> I was able to get the server to show the expected results. I enabled
> advertising on interface 4; added a route to fec0:0:0:1::/64 on interface
> 4
> and set it to publish; I showed the addresses and a new address was
> displayed.
>
> I've added a few new machines to my subnet; I went to the original XP
> client
> and did a show address but no new address was displayed. I went to the
> non-server 2003 machine and also no new address was displayed. I might
> have
> dug myself in deeper but I tried issuing the set advertise=enabled and add
> routes on the client machines but it didn't add a fec0 address. I tried
> issuing a ping to the new address on the server machine (from client
> machines) and get "Invalid source route specified"

Well, it looks like the server is working properly if it's given
itself an address based on your route.

On the server , just make a few quick checks:

(The screen-dumps here are a little fabricated, because my IPv6
infrastructure
is a little more complex than yours, and I've tried to chop it down to what
you should see. )

Show Route should show a line saying

Publish Type Met Prefix Idx Gateway/Interface
Name
------- -------- ---- ------------------------ --- ---------------------
yes Manual 0 fec0:0:0:1::/64 4 Local Area Connection

Show Address should have a line like this:

Interface 4: Local Area Connection

Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Public Preferred infinite infinite
fec0:0:0:1:202:b3ff:fe2a:70c0
Link Preferred infinite infinite fe80::202:b3ff:fe2a:70c0

Does this look OK?

One thing I didn't have you do was to enable forwarding on the LAN interface
of the server. Since we're not actually forwarding anything, I don't think
that's necessary, but it's possible the server needs forwarding enabled
before it considers itself a router.

At the IPv6 prompt: set interface 4 forw=enabled adv=enabled

I don't know what you've done on the clients.
I'd un-install IPv6 , reboot, and re-install it, to restore the defaults.

Now, on the XP client, it should do a router solicitation and pick up the
route.

If not, try disabling then re-enabling the LAN connection in the Network
Connections folder. That should force a round of router solicitation /
advertising.

Then the client should look a bit like this:
( I've snipped the other interfaces.)

netsh interface ipv6>show route
Querying active state...

Publish Type Met Prefix Idx Gateway/Interface
Name
------- -------- ---- ------------------------ --- ---------------------
no Autoconf 8 fec0:0:0:1::/64 4 Local Area Connection

netsh interface ipv6>show address
Querying active state...

Interface 4: Local Area Connection

Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Public Preferred infinite infinite
fec0:0:0:1:202:b3ff:fe2a:70c0
Link Preferred infinite infinite fe80::202:b3ff:fe2a:70c0 

-- 
Best Regards,
Ron Lowe
MS-MVP Windows Networking

Relevant Pages

  • Re: Cannot get NAT to route in RRAS
    ... The basic problem is that you are using an ADSL modem on the server. ... I would suggest that you set up a demand-dial interface to act as the ... Static Route wizard, create a default route using this interface (ie put ...
    (microsoft.public.win2000.ras_routing)
  • Re: Cannot get NAT to route in RRAS
    ... ADSL Link was set as the Public interface in NAT, ... The static route also adds in fine using the ADSL Link interface, ... separate DNS server handles client’s requests, ... > Internet connection. ...
    (microsoft.public.win2000.ras_routing)
  • Re: IP Confusion
    ... interface for the destination address. ... timeout problems also. ... You probably need to add a static route that describes what can be ... > This server was replacing an existing server so I first took NIC 1 and ...
    (alt.os.linux.redhat)
  • Re: Changing ISP smoothly..
    ... I can add a second interface on a different subnet, to the server, and bind a second default route to that. ... I do know that once a server is bound to a given interface, it will return packets via that interface, so the question would be as to how to bind apache to both...aha. ...
    (uk.telecom.broadband)
  • Re: Bridging wifi to ethernet
    ... interface over to my eth0 interface so I can hook in all the ... wired ethernet users to get access to the WIFI networks DHCP server? ... The magic part I don't know how to do is "route and NAT". ...
    (Fedora)