No networking - new Windows 7 computer - TCP/IPv4 and TCP/IPv6 - Odd IPCONFIG results
No networking - new Windows 7 computer - TCP/IPv4 and TCP/IPv6 - Odd IPCONFIG results-----------------The computer is Windows-7 64-bit.I'm on Comcast - cable-modem.The router is a DLink gaming router. I've bypassed the router - that didn't help.I've been stuggling with this for days - and I DID connect once, briefly. If I recall, the connection just went bad - I was looking at pages, and then I clicked something and waited and waited (I think. I've been stressed by this, so I can't say that was exactly how it happened, but I think so.)-----------This is a computer I'm setting up for someone. It will ultimately be used alone, in a home, plugged into Verizon FIOS.----------My network, here when I'm working, is called DavidNet. I changed the workgroup from WORKGROUP to DAVIDNET.-----------------There is Norton Security on this new machine. Turning it off didn't help. (I might need to uninstall it - but that would leave me naked, except for the Windows firewall.)When I look at the Norton view - there have been 2 different results: An old result was that it saw my other computers, and presented them by name. I changed them all to Trusted. Now it sees the correct MAC addreses of the other computers.but not their names.It says I belong to "unknown network."---------This computer has 2 TCP/IP entries: TCP/IPv4 and TCP/IPv6.---------When I run IPCONFIG, I see: Connectinon-specific DNS prefix: blank Link-local IPv6 address: some long string full of numbers Link-local IPv4 address: 169.254.58.219 An address that means NOTHING to me. WHoIS says it is UNKNOWN. Subnet mask: 255.255.0.0 Default Gateway: blank-------------------Other things I've tried: Assigning and address on my private network: 192.168.0.125 RELEASE and RENEW. I think it hung on RENEW.
December 7th, 2009 5:45am

169.254.0.0/16 is reserved for auto-configuration of a network when DHCP is unavailable:http://en.wikipedia.org/wiki/Link-local_addressIf you plugged directly into the cable-modem, perhaps you need to wait for the DHCP lease to expire before trying to obtain an IP. Each lease would be tied to a specific MAC address for its duration.To release a lease, you would run the following command on the machine connected to the cable modem that originally obtained an IP (since most ISPs only give you one):ipconfig /releaseIf the router was connected, then connecting it to the cable modem and going through the release process should make an IP available. Usually there's a button/link in the web administration pages to do this.
Free Windows Admin Tool Kit Click here and download it now
December 9th, 2009 9:48am

Hi, Please also try the following: 1. Please ensure that your NIC driver is up-to-date. 2. Upgrade your routers firmware. If the issue persists, please feel free to let us know.Thanks.Nicholas Li - MSFT
December 14th, 2009 1:31pm

I suspect you have the same issue as I do. Win7 and wireless don't work very well together recently. For me (and two others)it worked flawlessly last time, som 3 weeks ago, but not now.As a test try this: Disable WPA security or any security on the wireless acces point. Try to connect again.With security enabled, try this: Uncheck the IPv6 in the properties for the wireless card and then manually configure IPv4 with a fixed IP, gateway and DNS.Both these works for me with Win7 pro/ultimate 64 and 32 bit, Intel PRO/Wireless 3945ABG and Cisco access points.
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2009 1:16am

Hi Setting a computer on a Home network while using a router is more and issue of adapting the computer to the Router, rather then setting any thing special on the computer per-se Since the computer is going to end up on a FIOS Network, some of your current attempts might turning up Not helpful later on. In principle, if the Network card on the computer appears with No errors in the Device Manager you should leave it as is, and wait for the New environment. That said, I would get rid of the Norton software. Swicthing it Off does not mean that it is Not interfering with the Network stacks. The computer is going to be on a Router, the combination of a Router and Win 7 native software Firewall is excellent protection. In addition Win7 has Windows Defender (Anti Spyware) already installed. All you have to do is download the Security essential (Anti Virus) and you have full free protection that work well together. http://www.microsoft.com/security_essentials/default.aspx
December 15th, 2009 1:58am

I agree with Jack. Uninstall the Norton software. If you're concerned about lack of antivirus protection, disconnect your router from your cable modem while you are testing this computer. One problem you have -- as indicated by the 192.254.58.219 IP address and the blank default gateway address -- is that you are not authenticating to the router. That is, the router's encryption settings (or other "security" settings) are not permitting the computer to connect. It is usually best temporarily disable encryption on the router when setting up wireless networks. I would also -- permanently -- disable other forms of wireless "security" such as MAC address filtering or disabling SSID broadcast. Once you get the wireless connection established, then you can add encryption. With the router disconnected from the cable modem, you can test for connectivity by attempting to access the router itself (see default gateway for IP address). After you get the wireless issue fixed (or before, if you just connect the computer to the router with an Ethernet cable), then you can determine if the inter-LAN communication issue is fixed, either with or without Norton installed.
Free Windows Admin Tool Kit Click here and download it now
December 16th, 2009 4:06am

That is not correct. You cannot conclude that the the router doesn't authenticate the PC.My pc got authenticated, or to rephrase when the wrong key were typed in the router returned an error. With the right key it just ended there with no IP adress set on the PC. In fact I got traffic going by using fixed IP adress typed in manually. Maybe that'sthe way to work around the encryption as well? :) No seriously, as far as I'm concerned this is an issue of autmatic setup of TCP/IP configuration by Windows 7. The problem startetafter the latest security update and it involves even wired networks in some senarios. The fix was the same. Manually set IP adress. Clearly this is a windows 7 issue regarding automatic nettwork configuration.
December 16th, 2009 2:14pm

If the hardware used is NOT on the MS compatibility list you use it at your risk.There is NO issue when using hardware on the list. So there is no windows 7 issue to address.http://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspx
Free Windows Admin Tool Kit Click here and download it now
December 16th, 2009 6:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics