Vista 32bit network problems.
Experienced user here, reduced to the point of banging head against the
wall and spamming forums with my issue hoping for some luck. I'll try
to make this as detailed as possible, complete with an image.Problem: (Nutshell) My desktop computer cannot connect to the home network, and thus, no internet.Details:Other computers connect just fine, both wirelessly and wired, thus the modem and router are not to blame.Spontaneous
failure. Worked fine in the afternoon, in the evening (without an
update or restart in between) it would not connect to the internet.Network
and Sharing Center states that it can connect to the network (which it
has always listed as 'unidentified network' in this particular panel),
however attempts to access the router or modem via 192.168.1.1 or
192.168.0.1 respectively both fail.The following image includes
useful information for I hope somebody to help pick out the issue. My
attempted solutions, all which have failed will continue after.Image
contains cmd prompt with ipconfig/all and a ping of yahoo.com, Network
and Sharing Center, Local Area Connection Status, Network Connection
Details.When
clicking the "x" between unidentified network and internet, Windows
network diagnostics offers the following: Plug a cable into the network
adapter "Local Area Connection 2', Automatically get new IP settings
for for the network adapter "Local Area Connection", and A problem with
your network router or broadband modem might be preventing an internet
connection.All three of these issues seem to be red herrings.
My motherboard (full system specs to follow) contains two network
adapters, (1 and 2, for argument) and this solution pops up for
whichever adapter isn't currently connected to the ethernet cable to
the router. It also doesn't appear when the disconnected adapter is
disabled. The Automatically get new IP settings choice, always fails
to correct the problem. the third points me to the help dialogs, which
are of no use.I briefly received errors similar to the one stated here http://www.vistax64.com/drivers/113686-windows-32-bit-nforce-networking-controller-issue.html
however, since following solutions in that and other similar threads,
that particular error has stopped occurring. (And while it pointed to
the nforce controller, I never actually recieved the error31 in the
device manager, which never acknowledged that the devices were
malfunctioning.I've also attempted to update the drivers,
downgrade the drivers, switch from the nvidia nforce networking
controller to the microsoft default. I've attempted to uninstall and
reinstall the drivers and software, and manually remove teh driver from
the system32 drivers folder. Many restarts later, still no luck.I've
seemed to narrow it down that it is a computer issue and not a network
or modem issue, although I have also attempted to reset and power cycle
both the DSL modem and the linksys router, without complication, as the
laptop I'm currently typing on is successfully internet connected.My
confusion other than why this is happening at all, is that the computer
claims to be able to connect to the network in the network and sharing
center page, but not the network to the internet, as the other
computers can connect to the internet, and the desktop cannot access
192.168.1.1 (the linksys router).Further attempts at forcing
the network adapter into fulltime 100Mbps full duplex mode, and
switching the IPv4 and IPv6 to their alternate settings, as suggested
by some other forum posts to which I can't remember the addresses have
also failed.The only progress I've seemed to make is to
eliminate some obvious issues, and remove the NVIDIA nForce related
error. I did install the nforce_winvista32.15.08_english file which
was apparently the update to the adapter, but after further failures
and more forum reading I did a system rollback several days previous,
to remove it and any other recent updates, so that should be a
non-issue. The computer is currently at an 'update-state' at which it
should be working flawlessly, yet it is not. Thus my frustration.The computer itself is as a home-built machine:Asus Striker II NSEIntel Core 2 Quad 2.4ghz CPU at stock clock speeds4.00GB Corsair XMSSystem Disk is a 74GB WD RaptorAdditional Disks are WD Caviar 500 and WD Caviar 1000 GB disksnVidia 8800GTS x 2 video cards linked in SLICoolermaster 1000W PSUSoundblaster X-Fi Extreme Gamer AudioAll
wrapped in a Kandalf LCS case liquid cooling the processor, with a
second, separate liquid cooling circuit taking care of the video cards.I
use my computer for work and school (Architectural Design), and without
an internet connection, things are going to be rather difficult for me.Its my baby, and it doesn't love me right now. Help me?And
thats about where I am at the moment. Other than another forum post
suggesting that I download an nVidia Chipset Drivers file, which for
some reason doesn't recognize Windows as being Windows, so it refuses
to install, thus modifying nothing. Any input is appreciated at this
point.Additional:Connecting the ethernet cable to different ports on the router fails, as does connecting it directly to the modem. Several
restarts fail to knock anything loose so to speak, nor does leaving it
off for approximately 8 hours and starting up again.There is no
wireless internet built into the computer, and while I have the ability
to install a wireless card as a last resort, I'd have to replace the
audio card, which, naturally I'd like to have installed, not to mention
the superior performance of using a wired connection. So that seems to
be a last resort, however, I may have to try it if it would allow me to
ask Vista to automatically scan the internet for a fix of some sort.
But I won't do it unless somebody here suggests it might be fruitful,
since adding the wireless card is a temporary fix and not a permanent
solution.And.... thats about all I can think of right now. If I'm leaving out any pertinent detail let me know.Solutions
:-), questions, advice, all welcome, nothing is too small or too silly
a "have you tried this?".... I'm at the bottom of the barrel, and I
appreciate any and all help. After this comes paying somebody way to
much to try the things I've already tried.-TurboNitroMonkeyTurboNitroMonkey@gmail.com
January 1st, 2009 2:02am
Hi,From your screenshot I can see that the computer is unable to get an IP address:169.254.x.x is the automatic private P adressing, which the computer uses whener it is not assigned a static IP address or it cannot contact a DHCP server to get an IP address.For starters, please go to Network and sharing center > Manage network connections > right click the connection you are using > Properties > double click on IPV4 > set the IP address 192.168.1.9 subnet mask 255.255.255.0 Gateway 192.168.1.1 and as nameserver put208.67.222.222 and 208.67.220.220 Tell us how that works out.
Free Windows Admin Tool Kit Click here and download it now
January 1st, 2009 4:09pm
YounGun said: Hi,From your screenshot I can see that the computer is unable to get an IP address:169.254.x.x is the automatic private P adressing, which the computer uses whener it is not assigned a static IP address or it cannot contact a DHCP server to get an IP address.For starters, please go to Network and sharing center > Manage network connections > right click the connection you are using > Properties > double click on IPV4 > set the IP address 192.168.1.9 subnet mask 255.255.255.0 Gateway 192.168.1.1 and as nameserver put208.67.222.222 and 208.67.220.220 Tell us how that works out.I did the above, and the results for Windows Network Diagnostics are: "Cannot communicate with Primary DNS Server(208.67.222.222)" "Network diagnostics pinged the remote host but did not receive a response." It presents me with the options: A problem with your network router or broadband modem might be preventing an internet connection, and gives me the power cycle suggestion, Change the settings for network adapter "Local Area Connection", and Reset the network adapter "Local Area Connection". Oh my. Well, not quite lions and tigers and bears, but I'm still in the jungle. Where to go from here?Thankye kindly, and keep those suggestions coming.-TNM
January 2nd, 2009 2:57am
Hi,Open a command prompt (run > type: cmd) and issue the command ping 192.168.1.1 . What do you get? Can you also try to visit the router's admin interface?
Free Windows Admin Tool Kit Click here and download it now
January 2nd, 2009 11:21am
Hi,
Thank you for your post.
Based on my research, Id like suggest you try the following:
1. Update device driver for the NIC. (Please check the updates for both NVIDIA and ASUS. Meanwhile, you can also contact their support regarding this issue, if it is needed.)
2. We can also check the issue by manually assigning IP address, subnet mask, default gateway and the DNS settings according to your routers settings (You can also do this according to the network settings of other computers which are connected properly and just change the IP address and please also make sure that they are in the same subnet). Please let me know if this works.
If this still exists, it can be caused by the factor that the Vista cannot obtain an proper IP address and please refer to the following KB:
Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers
http://support.microsoft.com/kb/928233
After checking, if the issue persists, please help collect more information:
1. Please check the event log. Is there any related error message?
2. Based on my experience, the issue may be related to the device drivers of the wireless chipsets and the firmware of the wireless router. Therefore, I would like to suggest that you also check your wireless router manufacturers website and check if there is any upgrade version of firmware.
3. Please check if you have any other NICs (including virtual, wired or wireless). If so, please try to disable them in the Control Panel-Network connections or remove them from the device manager to have a check (Please make sure that you have driver before removing).
Hope this helps.
Nicholas Li - MSFT
Nicholas Li - MSFT
January 2nd, 2009 2:17pm
Hello, I hope the following information can help.....but try the following steps:1. Firstly , try to ping the routers IP address by attempting theses tasks - hold the windows logo key and tap on the letter R on the keyboard, this will open the command prompt. in the command prompt, type Ping 192.168.1.1 By doing this you wil get either of two responses; Request Timed Out or Reply. 2. If you get a Reply - thats a good sign, if you get request Timed Out......BAD3. If you got a reply, attempt the this troubleshootng step, but this time type the following in the command prompt - Ping 4.2.2.2 this is the global DNS Server and let us kow what was the result. What we are trying to figure out here is at which location the connection is failing. If you get a Reply when pinging the Global DNS, put the 4.2.2.2 address as the perfered DNS server and try opeining you web browser. With Vista, you sometime have to reboot the machine or disable and reenable the machine LAN Connectionfor the setting to take effect, best thing for you to do is reboot after you add the DNS server to your Prefered DNS setting.Note: the problem is that you computer has nt been assigned an IP address and is tryin to find something called a DHCP serever to give it one, you have two options here 1. Configure your routerto assign IP Address information or manually assign it yourself on the computer (recommended option). The second error you got was no DNS server available, try assigning the Global DNS server if you can ping it and this shouls help. Worst case senario is, you may have to reset the router to factory default and start the entire network configuration all over again. I hope this helps, if it dosen't send me an e-mail at a_maha@msn.com
Free Windows Admin Tool Kit Click here and download it now
January 3rd, 2009 4:47am
Thanks for all the posts, Ill respond to them in more or
less the order suggestions come up, for clarity, which will also be
sequentially how I act, so backtracking is possible if necessary.
Pinging 192.168.1.1 responded with 4x Reply from
169.254.73.210: Destination host unreachable. Followed by Packets: Sent 4, Received
4, Lost 0.
I am still unable to reach the router or the modems UI from
the desktop, although I can access the routers interface through a wireless
source, or wired through a laptop, and the modems UI through direct wired
connection from a laptop, as per usual.
I have been unable to locate any applicable driver updates,
some were found for the included and unused soundcard, and for raid
controllers, again not applicable. Ive located updates for my video cards as
well, from nVidia, however, again, not applicable to this particular
problem. Ill hold off on patching
extraneous devices until we solve the core problem, the networking interface
failure.
Attempts to manually set my NIC to the routers settings,
failed with the error Cannot Communicate with Primary DNS Server(192.168.0.1). When setting values, I chose the ones from
the Router tab of my Linksys interface as found at 192.168.1.1.
Data provided below, please note these are copied and pasted
from the Router status, and the settings reflect functioning, working,
successful values for all computers on the network, save for the desktop which
inexplicably and spontaneously failed to connect and now remains in that state.
Firmware Version: v4.21.1, Nov. 6, 2006
Current Time: Mon,
05 Jan 2009 14:12:06
MAC Address: 00:0C:41:75:E0:B2
Router Name: WRT54G
Host Name:
Domain Name:domain_not_set.invalid
Configuration Type
Login Type:
Automatic Configuration - DHCP
IP Address: 76.199.168.48
Subnet Mask: 255.255.255.0
Default Gateway: 76.199.168.49
DNS 1: 192.168.0.1
DNS 2:
DNS 3:
MTU: 1500
**Step Skipped: Before following the instructions at http://support.microsoft.com/kb/928233 and
editing the registry, I read through it and that issue doesnt seem to apply to
my situation, given that my problem doesnt envolve changing OSs recently,
that both XP, Vista 32 and Vista
64 have successfully connected to the internet, and the desktop connection spontaneously
failed. Personally, Id rather not screw
with the registry unless I know for sure it is the culprit, or that it is
easily undone should it be a required check.
Im under the mindset of if it aint broke, dont fix
it. So Im hesitant at the moment to try
updating or changing anything from the settings of the functioning router and
modem at the moment. They are working as
always, for every computer but the desktop.
If I monkey with the settings in them, chances could be that Id have to
start troubleshooting them to get ANY internet connection in the house
functioning before I return to the desktop.
Occams razor, the simplest explanation is often the best, the problem
is clearly with the desktop computer, not the laptops, the network or the
modem. Im going to stick to trying to
fix that, unless somebody gives me an argument to the otherwise that seems
logical enough to try, with low enough risk that Ill be able to fix anything
that goes south :-P
So Nicholas Li, I thank you for those suggestions, but for
the time being Im going to try other routes of attack.
Regarding your suggestion 3: I have done so to no avail.
Disable, remove, update and troubleshoot those connections, no dice. I had a virtual one for a while attached to
one of my Local Area Connections, but no longer. Local Area Connection 1 is being used, device
name NVIDIA nForce Networking Controller, its twin, Local Area Connection 2,
has either been active but not connected, or disabled, neither affecting the
performance of #1. Ive also switched
cables between the two, and gotten no difference.
Sigh. So Next post:
As stated earlier, Pinging 192.168.1.1 resulted with four
copies of the following Reply from 169.254.73.210: Destination host
unreachable. And then something to the tune of: Followed by Packets: Sent 4, Received
4, Lost 0.
When pinging 4.2.2.2, I get 4 results of:
PING: transmit failed, error code 1231.
And then the statistics are 4 sent and 4 lost, of course.
Still boggled, still stuck with an internet-less but pretty paperweight. So. Whats next? Anyone? Or do I need to start offering cases of beer to my savior? :-P-TNM
January 6th, 2009 1:52am
Next wave: Tried the following steps:1 Reset the IP settings to automatic2 Tried "netsh winsock reset catalog" and "netsh int ip reset reset.log" commands in cmd3 Rebooted the computer and router.No dice.Also, I attempted to simply restart the computer while the network cable was unplugged, as it apparently helped someone in another forum entry. Also failed.Please keep the ideas coming.-TNM
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2009 10:46am
Next try: Backed up the registry, followed the following to do the...To resolve this issue, disable the DHCP BROADCAST flag in Windows Vista. To do this, follow these steps: Click StartCollapse this imageExpand this image, type regedit in the Start Search box, and then click regedit in the Programs list.Collapse this imageExpand this image If you are prompted for an administrator password or for confirmation, type your password, or click Continue. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{GUID}In this registry path, click the (GUID) subkey that corresponds to the network adapter that is connected to the network.On the Edit menu, point to New, and then click DWORD (32-bit) Value.In the New Value #1 box, type DhcpConnEnableBcastFlagToggle, and then press ENTER.Right-click DhcpConnEnableBcastFlagToggle, and then click Modify.In the Value data box, type 1, and then click OK.Close Registry Editor.By
setting this registry key to 1, Windows Vista will first try to obtain
an IP address by using the BROADCAST flag in DHCP Discover packets. If
that fails, it will try to obtain an IP address without using the
BROADCAST flag in DHCP Discover packets.....thing as located:http://support.microsoft.com/default.aspx/kb/928233Also failed.I can undo it if recommended, but seeing as apparently its set to try doing it the original way if the new way fails, there doesn't seem much reason to.Next?-TNM
January 6th, 2009 11:17am
Hi,
Thank you for your response.
From your updated information, I found that the Windows Vista computer still got the APIPA (Automatic Private IP Addressing) address 169.254.73.210. Generally, if the system cannot successfully get a valid IP lease from the DHCP server, an APIPA address is used.
Therefore, it indicates that the problematic computer was still unable to get a valid IP address.
So, we do not need to try other steps such as change the settings in IE, or reset WinSock. Instead, we should focus the troubleshooting on DHCP side. Commonly, we need to focus on the three elements:
1. Router.
2. Network cable.
3. NIC.
To narrow down the issue, I would like to suggest the following at this time:
1. Check the router:
I noticed your router Firmware Version is v4.21.1, Nov. 6, 2006. After checking on the Linksys site, I found there are newer versions released and improved some functions. Thus, I suggest upgrading the Firmware to see if works.
(If you are afraid of make our issue worse by doing this, please also involve your routers manufacture for technical support. It is more safe to upgrade the Firmware or adjust the settings with their helps.)
2. The issue can also be caused by the factor that the network cable is damaged. Therefore, please connect the computer and the router with another cable to see if it helps.
3. Check the local settings.
1) Please understand an upgraded version of driver can fix some issues or improve the hardwares performance. So, please upgrade the drivers for the NIC via ASUS and NVIDIA.
2) From your router settings, I found the following information:
IP Address: 76.199.168.48
Subnet Mask: 255.255.255.0
Default Gateway: 76.199.168.49
Please ping 76.199.168.48 and 76.199.168.49 separately and let me know the results.
You can also manually assign the IP address such as 76.199.168.50 (if not in use) or some other IP address which are in the same network segment with 76.199.168.49, and input the Subnet Mask - 255.255.255.0 and Default Gateway - 76.199.168.49 as well. Please check if the connection works then.
3) Since the error message Cannot Communicate with Primary DNS Server(192.168.0.1) was received, it means the computer failed to contact with the DNS server. Please perform the following steps to manually assign a DNS address to the NIC.
a) Go to Control Panel - Network Connections.
b) Right-Click on the connection and click Properties.
c) Find Internet Protocol (TCP/IP) Version 4 in the list.
d) Click Properties, and then click Advanced
e) Go to the DNS tab, and click Add.
f) Type the IP Address 192.168.0.1
g) Click OK on everything and run Diagnose and repair again to check the issue.
Hope this helps.
Nicholas Li - MSFT
Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2009 2:37pm
Ok next set:
Bit the bullet:
After hellish searching, and then an accidental stumble onto
it it appears Ive found the upgraded nForce drivers. My LAN drivers are now NVIDIA nForce
10/100/1000 Mbps Ethernet dated 8/1/2008
and version 67.8.9.0.
Unfortunately after upgrade, Ive still noticed no
difference.
Dug around the linksys site and found the upgrade you
mentioned for my router, dated a few months newer than the firmware version I was
currently using. Unfortunately, after the
upgrade it seems that the new version is exactly the same as my old one: v 4.21.1
Nov 6, 2006, despite being
listed as a January release. So that
proved to be no help.
My Router is the WRT54G V1.1 if that helps at all.
Again, no difference.
Swapped cables to a tested working cable, no effect. Tested my current cable in the same manner
(disabled wireless network in my laptop and wired it to the router). No dice.
Pinging 76.199.168.48 responds with some curious results. 4
sent, 4 received, but it gives me four copies of Reply from 169.254.10.42:
Destination host unreachable. So I ping
one address and it gives me a reply from another? What?
Pinging 76.199.148.49 gives identical results, Unreachable
host from the 169.254.10.42 IP.
I then set the manual IPv4 settings you suggested, again to
no avail.
The Windows Network
Diagnostics for all these situations has typically been either Cannot Connect
with Primary DNS server, Windows tried a repair but a problem still exists,
or There might be a problem with one or more network adapters on this computer. It then suggests That I change the settings
for the current network adapter, that I plug in the currently disconnected
network adapter, whichever that happens to be at the time, that I automatically
get new IP settings for the network adaptor which IS connected, or that A
problem with my network router or broadband modem might be preventing an
internet connection, and that I should power cycle them and try again.
All those still fail.
After a doublecheck to linksys router status page, I noticed
that the IP addresses provided were a little different, in the 76.199.163.208
area. So I retried the previous steps
with the new IP addresses. Same issues:
Cannot connect with primary DNS server 192.168.0.1.
Still in the dark ages with that particular box.
What am I missing here? :-/
I appreciate all the help.
Whats left. Hardware
failure? But if it was that it likely
wouldnt recognize being plugged in or disconnected anyways. Id have to have to replace the motherboard,
Ive already done that once in this computer, this one is relatively new.
Replacing the router would be cheaper and easier, but given
that Im writing this on a laptop with a functioning internet connection
through it, I find it difficult to think that it is the fault of the router or
modem.
Thoughts? Suggestions?
So far so good, were narrowing down a lot. And at this point I find it difficult to
believe that taking it in anyplace would have given it this depth of thought
and not come back with anything other than replace your motherboard wuss-out
answer.
Lets see. Another
<$ solution would likely be what? Purchase a PCI NIC, and see if I can
connect through it?
That would of course assume spontaneous simultaneous failure
of both network connections built into the motherboard.
Ah well, my ears are open, no matter how silly, lay it on
me.
January 7th, 2009 3:03am
Hi,
Thank you for your update.
May I know the exact model and brand of your network adapters on the problematic computer, and were you able to connect this same computer to Internet before? Also, I have noticed that other computers connect to the Internet properly, please help me collect the following information on one of these good computers (if possible another Windows Vista computer is preferred) with the following steps:
Run CMD and then ipconfig /all to export all the network settings and post the information to this thread.
After obtaining the information, I will check its settings and help you adjust the settings of problematic Windows Vista computer.
Meanwhile, please also contact your router manufacture for technical support and let them help you adjust the router and clients settings properly.
I look forward to your reply.
Thanks
Nicholas Li - MSFT
Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2009 2:05pm
The network adapters are the dual onboard adapters to the ASUS Striker II NSE MoBo:Motherboard's Page on the ASUS SiteAnd this computer has been on the internet successfully for around 15 months, save for a short period where I had to replace the motherboard and power supply (and RAM), a task I'd rather avoid doing again for financial and headache reasons. That change happened approximately 3 months ago, and again the network was never an issue until about 6pm on 12/31/08, when it worked perfectly at 2pm 12/31/08, with no shutdowns or restarts or updates in between.Anyways, the other computers routinely on the network are an HP laptop running Vista64bit (this one I'm using at the moment to write this) and a slightly older Dell running XP.The ipconfig /all dump from the Vista64bit HP follows:Microsoft Windows [Version 6.0.6001]Copyright (c) 2006 Microsoft Corporation. All rights reserved.C:\Windows\system32>ipconfig/allWindows IP Configuration Host Name . . . . . . . . . . . . : TurboNitroMo-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain_not_set.invalidEthernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 00-1D-72-69-54-FA DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesWireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : domain_not_set.invalid Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN Physical Address. . . . . . . . . : 00-21-00-3A-53-74 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b0f5:d928:13f4:e5e8%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, January 07, 2009 4:07:16 AM Lease Expires . . . . . . . . . . : Thursday, January 08, 2009 4:07:16 AM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 NetBIOS over Tcpip. . . . . . . . : EnabledEthernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 00-21-86-70-09-D1 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 7: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{37784012-5F6E-45B7-82F1-13DC20E02F22} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : domain_not_set.invalid Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{472A8D24-1E10-4D05-BFBB-7E56F45310F7} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 19: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesC:\Windows\system32>This is once again from the functional laptop, not the malfunctioning desktop computer, as asked. What are the odds, on a sidenote, that reinstalling Vista would provide a fix for this issue?-TNM
January 8th, 2009 12:01am
Hi,
Thank you for your efforts and the information.
Lets go ahead and adjust the network settings to narrow down the problems scope:
Manually adjust the network settings
=======================
1. Go to Control Panel - Network Connections.
2. Right-Click on the connection and click Properties.
3. Find Internet Protocol (TCP/IP) Version 4 in the list and click Properties.
4. On General tab, select Use the following IP address and type in the IP address, Subnet mask, Default gateway as the following:
IPv4 Address - 192.168.1.110 (If this one is in use, please choose one IP address in the same subnet with 192.168.1.103.)
Subnet Mask - 255.255.255.0
Default Gateway - 192.168.1.1
5. Select Use the following DNS server address and type in the DNS server address as following:
DNS server address - 192.168.0.1
6. Click OK on everything and run Diagnose and repair again to check the issue.
After performing the above steps, if the issue persists, please run ipconfig /all to export the network settings on the problematic computer and post the information to this thread. I will perform further research.
Thanks.
Nicholas Li - MSFT
Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2009 2:08pm
Followed your most recent instructions, Nicholas, and it came up with the same error as always: "There might be a problem with the network adapter "Local Area Connection"." A problem with your network router or broadband modem might be preventing an Internet connection. Change the settings for network adapter "Local Area Connection" Reset the network adapter "Local Area Connection"Microsoft Windows [Version 6.0.6000]Copyright (c) 2006 Microsoft Corporation. All rights reserved.C:\Users\TurboNitroMonkey>ipconfig/allWindows IP Configuration Host Name . . . . . . . . . . . . : Kandalf Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Local Area Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce Networking Controller #2 Physical Address. . . . . . . . . : 00-22-15-03-6E-B8 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesEthernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet Physical Address. . . . . . . . . : 00-22-15-03-6E-B7 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::70da:19a4:ec37:4006%8(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.110(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 7: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{73DE7276-ADA0-453B-9044-62D7DF1BECFE} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesC:\Users\TurboNitroMonkey>Additionally, getting properties on. augh, now I can't remember how exactly, gleaned this jewel:Component GUID: {7071ECA3-663B-4BC1-A1FA-B97F3B917C55}
Component file: [C:\Windows\system32\connect.dll]
Error: (0x800706BA) <The error message could not be found>.
Additional info:
Failed to detect Internet connectivityif that helps.Sooo....I took the next next step and reinstalled Vista 32-bit, instead of continuing to monkey around with the IPs, which still seems like a temporary fix for a permanent problem (There is no reason why it SHOULDN'T autodetect the IPv4s when two weeks ago, and every day before it required no input and autodetected everything). Upon the reinstall, same issue continues, leading me to believe it might be a hardware issue with the physical adapters, even though that sends up a few red flags in my brain. Flags like:Theres two of them with the same problem.It detects when I plug/unplug it from the router.So what I'm going to do is print out this thread take it to the local Comp/Network fixing place, and bounce some ideas off them. 2 weeks is long enough without being able to use this box on the net.Then... unless they can come up with some miracle, my next step is to spend $20 on a PCI NIC. If that works I might just call it a day without a proper solution, and spend another $60 to get an audio card for my small PCIE slot.That being said. If there is some sort of epiphany in this community, and especially from you Mr Nicholas Li. And we can yet get the computer to work properly sans new hardware, within the return frame of when I buy it (in the next day or two). I'll happily return it for a refund an mail you a case of beer. Or at least something to the effect. Your effort has been most valuable to this frustrated nerd.Thoughts? suggestions?
January 14th, 2009 2:49am
Hi,
Thank you for your response.
I know there are two NICs integrated on the motherboard. May I know what the results are after trying these suggestions with the other NIC?
At this time, please try the following:
1. Disable IPv6
========
1) Go to Control Panel - Network Connections.
2) Right-Click on the connection and click Properties.
3) Uncheck the Internet Protocol (TCP/IP) Version 6 in the list and click OK.
4) Please reboot the computer to see if it works.
2. Please check if you can access the router
=========================
1) Please try to access the routers management site.
2) Ping your router with IP address to see if it works.
3. Please connect the computer to the Internet directly (bypass the router) to check the issue.
Please let me know the results.
Thanks.
Nicholas Li - MSFT
Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
January 14th, 2009 1:42pm
Woo Hoo, been trying for a week to get my ista home computer to connect to internet. don't know why it quit working, don't care! 2 computers just stopped connecting. Got notepad back on line fairly easy it's XP. Not computer smart just able to read. Your
reply was to the point, simple to follow and worked. THANK YOU THANK YOU THANK YOU Now is there any way I can fix the letter that's between the letters u and w? It doesn't work while
typing and a whole line of them show up when I click on the place for user names and passwords. I hae to delete them before I can type in them.
April 21st, 2012 11:38pm