connected to network no internet access

reddgsx · 20 Nov 2009

all of the lines had a # sign, i went under the hosts file not the host.ics right?

ok so i flushed the DNS said it was successfully flushed

then i registered and it said registration of the DNS resource records for all adapters of this computer has been initiated. any errors will be reported in the event viewer in 15 minutes.

i tried the internet and still nada, i just rebooted and no internet. (idk if i was supposed to do this but i was just trying to save a reboot comp post)

i appreciate your help soooo much if i could tip you i would

also i went to comcast support live chat and they asked about my router and i told them dlink dir655 and then she gave me a url to my personal router info and told me to go to the website on the "affected" computer and i said how?! i cant go on the internet, and they said just try it so i did then they were like sorry we cant help its a router problem call dlink i didnt call dlink yet.....they wanted to change my WEP key

ya i dont know what any of this stuff means so im glad you can give good directions

patwhatsthat · 20 Nov 2009

I don't think that changing your WEP security for your wireless network would have impacted this issue since from what you have told me so far it involves a wired interface. Well since everything was going good until yesterday, or is that day before now...we could try a restore point. We could try removing and reinstalling the problematic nic, not physically but virtually through device manager, we could try replacing the nic with a known working one. And probably what I should have asked way earlier is, did you, on that faithful day install any type if internet security suite software, or perhaps some type of software VPN solution, if so try uninstalling and see what happens

reddgsx · 20 Nov 2009

i didnt install any new programs or software, this is a brand new computer like 3 weeks old, i have barely anything on it as it is, before i even thought of anything i was going to restore it but the last restore point doesnt allow me to load it.....when i clicked on it nothing happened.

i dont understand why it just magically stopped working that doesnt make any sense.

so are you saying the only thing i can do now is restore or some type of recovery cuz that would suck.

patwhatsthat · 20 Nov 2009

good to know...although if you can't use a restore point, and I will assume you have tried more than one, that may suggest something different is going on. Did you try to open device manager and uninstall the offending network card and reboot your computer and see what happens. I didn't say that a restore or recovery was the only options...but it seems that options are growing more and more limited. You might try system file checker just to see if that would help...from a command prompt (click start>all programs>accessories> right click on command prompt and choose run as administrator) type sfc /scannow

raphytaffy · 20 Nov 2009

Hi Pat, I'm having issues connecting to my internet as well. Ethernet connection works just fine, but I am unable to get the wireless to work. Here is my log from ipconfig /all:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Hien>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : HIENLAP-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network Conn
ection
Physical Address. . . . . . . . . : 00-12-F0-4E-83-51
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e9e6:ed72:1f31:1c3%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.87(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, November 20, 2009 1:02:54 PM
Lease Expires . . . . . . . . . . : Saturday, November 21, 2009 1:06:07 PM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 318771952
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-98-B7-22-00-C0-9F-8C-50-08

DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
NIC
Physical Address. . . . . . . . . : 00-C0-9F-8C-50-08
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.gateway.2wire.net:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

patwhatsthat · 20 Nov 2009

raphytaffy:
just checked your specs and see your running Win7 ultimate but it doesn't say which version. You need to update your system specs. And some more information would be helpful. Checked intel site for lates drivers and there is nothing I can see for Win7...there are some Vista 32 bit drivers and some xp 64 bit drivers. So going out on a limb here and guessing....drivers? There are some really great people here who are good at providing driver information help...so hang in there and maybe someone else will contribute.

raphytaffy · 20 Nov 2009

Pat, I am running on 32-bit Windows 7 Ultimate. After the install, Windows update automatically installed updates for various components on my system via ethernet. Among those updates were settings for my wireless: INTEL PRO/Wireless 2200BG Network Connection. I thought that since Windows was able to recognize this component and install it that everything should be up and running smoothly.

patwhatsthat · 20 Nov 2009

Yep...that would be a logical assumption and it most case would be a correct one, but if you've spent anytime surfing this forum you'll see that that is not always the case. Since you didn't actually say what your exact problem was perhaps you could begin by explaining what you can and can't do when you are using your wireless device. Can you ping other devices on your local subnet by ip and or name, can you ping and outside ip address like 4.2.2.1, can you ping a fully qualified domain name like www.google.com. Maybe it would be better if you started a new thread with your device name as the title Intel(R) PRO/Wireless 2200BG and a brief description of your actual issues and what you have tried

raphytaffy · 20 Nov 2009

I had a thread for this under the drivers section, but didn't get much help so I thought maybe it wasn't a driver issue but something else that I'm missing. Haven't tried much in terms of diagnosing the problem as I don't really know the steps to do so. All I know is that the ethernet works, wireless doesn't. Here's what I got when I tried to ping 4.2.2.1:

C:\Users\Hien>ping 4.2.2.1

Pinging 4.2.2.1 with 32 bytes of data:
Reply from 192.168.1.87: Destination host unreachable.
Reply from 192.168.1.87: Destination host unreachable.
Reply from 192.168.1.87: Destination host unreachable.
Reply from 192.168.1.87: Destination host unreachable.

Ping statistics for 4.2.2.1:
Packers: Sent = 4, Received = 4, Lost = 0 (0% loss)

patwhatsthat · 20 Nov 2009

OK so you can't reach anything on the outside edge of your router how about when you ping 192.168.1.254 which is the inside edge. Did this thing ever work?