Seeking advice per configuring VISTA(64) to my LAN

[BonzaiDuck]

I've had this set of problems before, but they are "benign."

Under Win 2000 and XP for some four or five machines, using the DHCP server-feature of my LinkSys router generated warnings or "red" errors that a DHCP lease had expired, or could not be found. Yet, network connectivity continued.

I discovered -- as I imperfectly recall -- that it was easier to hard-code fixed IP addresses for each computer within the LAN subnet mask/range of the router.

Now, I've configured two of the machines with VISTA-64. I think I'd discovered with XP that a new network-protocol layer or driver had been added to default configurations: In addition to IPv4, there is IPv6.

I allowed VISTA to auto-configure the system to both internet and my LAN through the router. I had left the router setup to provide a sub-range of addresses through its DHCP server -- which -- in the long run -- the other computers do not use.

The VISTA event-viewer system-log reports the following errors and warnings:

NVENETFD (source) Event ID 5008 "NVIDIA nForce 10/100/1000 Mbps Ethernet : Has encountered an invalid network address."

Dhcp_Client (source), Event ID 1003 (Warning) "Description for . . 1003 from source M_S_Win_DHCP-Client cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted . . . . . "

followed by:
Dhcp-Client (source), Event ID 1002, "The IP address lease 192.168.1.xxx [in the DHCP-available sub-range] for the network card with . . address xxxxxxxxxx has been denied by DHCP server 192.168.1.1 [the router/gateway address] (The DHCP server sent a DHCPNACK message.)"

Further, looking at "Local Area Connection Status" shows: "IPv6 Connectivity: Limited."

The router's PnP configuration option has been turned off -- something I'd done to simplify configuration for client-end machines using the earlier OS's. I think at one time, I had an XP installation that was all fouled up with additional "items" under "Local Area Connection Properties" -- which I uninstalled or disabled. However, since then, all the XP computers have kept their original LAN Connection items from the time of OS installation, but they've been set up with fixed IP addresses. The VISTA machines still get their IP addresses from the router's DHCP.

My file-server is still running Win 2000 Pro, but I was able to share (using machine-name, IP address and share-name) folders on the server so they're accessible to the VISTA machines.

So MY QUESTIONS:

"If I want to use fixed IP addresses for the VISTA machines, would I configure the IP4 and IP6 properties the same way -- with the same IP address, same gateway address, same DNS server addresses, etc.?"

"Should I enable the router for PnP?"

"What else should I do to tie up loose ends with these machines?"

"What else do I need to do to clean up the errors and warnings reported in my EV System Logs under VISTA?"

 

[sonoma1993]

you can enable the vista machines to use static IP addresses. IP6 uses hexadecmial for it's IP configuration. The UPnP from my understanding, allow programs to open/close ports on the router as needed by the program.

 

[JackMDS]

uPNP is considered a security risk it has nothing to do with your current problem, so unless you specifically need uPNP for something leave it off.

As far as the DHCP problem, maybe this can Help.

http://support.microsoft.com/kb/928233

 

[BonzaiDuck]

Originally posted by: sonoma1993
you can enable the vista machines to use static IP addresses. IP6 uses hexadecmial for it's IP configuration. The UPnP from my understanding, allow programs to open/close ports on the router as needed by the program.

Thanks to sonoma1993 and JackMDS.

If I use a static IP address to configure IPv4, what do I do regarding IPv6?

I assume that the decimal IP address segments -- for instance, the "245" in an address "245.128.0.5" would be convert to its own hexadecimal equivalent? And the remainder in succession?

And -- again -- do I use the same IP address for both IP4 and IP6?

Also -- why do I need the IP6 protocol/driver/configuration?

As for the Microsoft link, I'm saving it to my "Favorites" to get a closer look tomorrow.

Thanks again. Any further help will be appreciated.

 

[BonzaiDuck]

Well . . . Interesting. . . .

I apparently had done what is necessary on the first VISTA64 machine to set a static IP address, the gateway address, and the preferred DNS servers under IP4. The Local Area Connection Status window shows IP6 Connectivity as "Local" -- not "Limited."

I also noticed that the IPv6 properties still specified that it get an IP address automatically.

Setting up the second VISTA64 machine the same way changed "Limited" to "Local."

So the question remains: "How many of the errors and warnings on the event-viewer logs for the second VISTA 64 machine will disappear?"

I'll have to tinker with this some more. But I'm able to connect to XP systems in the house which are equipped with the LLTD Responder patch or service-pack 3. So everything seems to work the way I would want it to, except that the VISTA "Network" screen still only shows icons for the two VISTA machines.

 

[spidey07]

There is no reason for you to have IPv6 installed and active at all. That will eliminate much of your errors.

 

[BonzaiDuck]

There must be a VISTA version of a "bible" like the "XP Resource Kit." They used to sell the printed versions of Resource Kits -- for Win 2000 and XP -- in bookstores. I think the XP version was online. I should poke around and see what I can find, because it would probably explain much of this . . . . "new stuff."

But I'll take you at your word about IPv6 . . . .

 

[spidey07]

Originally posted by: BonzaiDuck
There must be a VISTA version of a "bible" like the "XP Resource Kit." They used to sell the printed versions of Resource Kits -- for Win 2000 and XP -- in bookstores. I think the XP version was online. I should poke around and see what I can find, because it would probably explain much of this . . . . "new stuff."

But I'll take you at your word about IPv6 . . . .

With vista MS disobeyed many internet standards. Specifically dealing with DHCP. JackMDS' link contains more information.

It's called the big dhcp bug with vista and they refuse to fix it.

Regarding IPv6 - not needed in anyway/shape/or form.

 

[BonzaiDuck]

Originally posted by: spidey07

Originally posted by: BonzaiDuck
There must be a VISTA version of a "bible" like the "XP Resource Kit." They used to sell the printed versions of Resource Kits -- for Win 2000 and XP -- in bookstores. I think the XP version was online. I should poke around and see what I can find, because it would probably explain much of this . . . . "new stuff."

But I'll take you at your word about IPv6 . . . .

With vista MS disobeyed many internet standards. Specifically dealing with DHCP. JackMDS' link contains more information.

It's called the big dhcp bug with vista and they refuse to fix it.

Regarding IPv6 - not needed in anyway/shape/or form.

Thanks, spidey07 --

Here's what I discovered, and what I've done so far. The number of red and yellow bang nodes in Event-Viewer logs has decreased -- as I would've expected.

The 780i VISTA64 machine had already been set up with static IP for IP4. No attention paid to default configuration for IP6, though -- it was still set to obtain addresses automatically.

So -- the machine of major concern here -- a 680i C2Q system -- I changed to static IP address for IP4.

[Ordered a Vista Resource Kit from Amazon -- @ 30% discount; They offer an online version for about $12.]

Consistent with the response views here, IP6 "penetration was still less than one percent of Internet-enabled hosts in any country." Apparently, it addresses concerns about "address saturation" worldwide, but I can't see how this is relevant to the address-space within a home LAN.

SO: Should I UNINSTALL IP6? Or simply UNCHECK the checkbox under its properties for the "LAN connection." I notice that unchecking it still leaves status information in the network status window showing "limited."