Page 1 of 2
Connectivity issues
Posted: Thu Jul 17, 2008 9:51 am
by unfaithfulsfan
I'm working on an HP Pavilion dv6000 that just will not connect to the Internet wired or wirelessly. It sees the wireless network and says the signal strength is excellent but has "limited or no connectivity" I tried using a USB adaptor to connect through a standard network cable and it says "Device cannot be started" I tried all the usual ipconfig parameters to no avail. Ping isn't working. I've updated all the drivers. The only thing I havent' done is remove the adaptors in Device Manager and let them reinstall
I'm kinda lost here. Is there a Registry setting that could be blocking all network connectivity?
Thanks
Jack
Re: Connectivity issues
Posted: Thu Jul 17, 2008 9:58 am
by Darkstar
Is it getting an ip address? or an auto IP? have you tried a release/renew on the ip address?
not sure on the registry, saw this setting but not sure of the use:
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\
Network Connections]
Re: Connectivity issues
Posted: Thu Jul 17, 2008 10:15 am
by unfaithfulsfan
It's getting the ip address. /release /renew had no effect. Ping is returning "transmit failed error code 65"
I tried that registry key and it's not there. In fact, there's no Windows folder under Microsoft.
I found something else I'm going to try. I'll let you know how it works out
Jack
Re: Connectivity issues
Posted: Thu Jul 17, 2008 11:41 am
by unfaithfulsfan
I followed MS's advice on reinstalling Winsock and Winsock2 then reinstalling TCP/IP Protocol and that did exactly squat.
Still open for suggestions.
Jack
Re: Connectivity issues
Posted: Thu Jul 17, 2008 11:42 am
by DMB2000uk
Try rebuilding the TCP/IP stack, in a command window (dos prompt) tpye:
You must specify a log file instead of <filename> for this to work.
Dan
PS. Though reinstalling the TCP/IP protocol could have done the same as this?
Re: Connectivity issues
Posted: Thu Jul 17, 2008 12:05 pm
by unfaithfulsfan
I'm sailing in uncharted waters, what logfile name should I look for and where?
Jack
Re: Connectivity issues
Posted: Thu Jul 17, 2008 12:10 pm
by DMB2000uk
Just something like C:\logfile will work.
Dan
Re: Connectivity issues
Posted: Thu Jul 17, 2008 12:15 pm
by unfaithfulsfan
looking at MS's page on the subject, I tried resetlog.txt. Don't know if that was correct but it didn't make any difference...
This is beginning to become a bit of a PITA. Ive been working on this thing for 6 hours straight.
Jack
Re: Connectivity issues
Posted: Thu Jul 17, 2008 12:21 pm
by unfaithfulsfan
He's got (@#!!$#@&%#$#@!!!) Norton on here that is not activated. I tried disabling the Windows firewall but got a weird response. In the firewall options, it says it's off, but in security center it still shows it as on. I'm wondering if Norton could be blocking access?
That's really grasping at straws I know. I'm hesitant to uninstall it but I'm seriously thinking about it.
Jack
Re: Connectivity issues
Posted: Thu Jul 17, 2008 12:38 pm
by Darkstar
If it has Norton 360 it could very well be blocking, i saw a reference somewhere (cant remember where) where someone had a similar problem....
i would do a uninstall of Norton, not sure of the situation might want the customers ok?
Re: Connectivity issues
Posted: Thu Jul 17, 2008 12:49 pm
by unfaithfulsfan
Yeah, I'll give him a call.....
Thanks,
Jack
Re: Connectivity issues
Posted: Thu Jul 17, 2008 1:42 pm
by Darkstar
Also if you havent tried to rebuild the IP stack like Dan suggested i would do that. As for the logfile you arent looking for one, the events from the rebuild will go there, so it doesnt matter what you use.... you can cut and past this if you want....
netsh int ip reset c:\iprebuild.log
Re: Connectivity issues
Posted: Fri Jul 18, 2008 7:45 am
by unfaithfulsfan
Well sh*t. (Sorry) That didn't work either. I also uninstalled Norton. I love my job. I always find out the rest of the story just when I'm ready to commit ritual suicide.
This computer has
never been connected to the Internet. Here I am running virus scans when I find that out. I'm beginning to think Factory Restore but bossy-boss says no.
I'm left to wonder about this other app that's installed. Are y'all familiar with Windows Registry Repair Pro? The customer just loves it so I can't uninstall it. I'm betting it has mucked up something in the registry but I don't know what or where.
Sometimes it really sucks to be me!
Thanks
Jack
Re: Connectivity issues
Posted: Fri Jul 18, 2008 8:25 am
by Darkstar
Have you checked that the NIC card is working (lights on connection)? and on the wireless did you select Windows to manage the device and turn off the vendor software? Is the hardware list clean? (No yellow or red marks next to devices) maybe you can run an IPCONFIG /ALL and post so we can see th network setup.
Re: Connectivity issues
Posted: Fri Jul 18, 2008 9:50 am
by Sporg
Maybe I missed, but did you try to ping yourself? 127.0.0.1 ?
Re: Connectivity issues
Posted: Fri Jul 18, 2008 10:14 am
by Sporg
I just did some "googling" and looks like this is a fairly common problem. After you've ruled out drivers and settings, you might hit the HP site and see if there is support (or even a recall) related to your problem.
Re: Connectivity issues
Posted: Fri Jul 18, 2008 10:29 am
by unfaithfulsfan
Darkstar wrote: on the wireless did you select Windows to manage the device and turn off the vendor software?
How do I do that? As to the others, Hardware list is clean, NIC card is working. I'll have to manually type in the IPCONFIG /ALL
unless I can figure out a way to sneakernet a copy to this PC. PING seems to be working now at least after the 5th time rebuilding the stack. I tried pinging myself and it worked. I can ping the router and I can ping yahoo. I know that's a sign I've almost got it whipped, unfortunately between the 10 mg Methadone and the 20 mg Lortab I can't remember what else to do now that PING is working.
Windows IP Configuration
Host Name........................................................DugglebyHome
Primary DNS Suffix...............................................
Node Type.........................................................Hybrid
IP Routing Enabled................................................No
WINS Proxy Enabled...............................................No
Ethernet adapter Wireless Network Connection 2
Connection-specific DNS Suffix..................................
Description.........................................................Intel PRO/Wireless 3945ABG Network Connection
Physical Address...................................................00-18-DE-7A-24-54
DHCP Enabled......................................................Yes
Autoconfiguration Enabled........................................Yes
IP Address...........................................................0.0.0.0
Subnet Mask........................................................0.0.0.0
Default Gateway....................................................
DHCP Server.........................................................255.255.255.255
Ethernet adapter Local Area Connection
Connection-specific DNS Suffix...................................
Description..........................................................Intel PRO/100 VE Network Connection
Physical Address....................................................00-16-36-98-E0-26
DHCP Enabled.......................................................Yes
Autoconfiguration IP Address......................................169.254.42.198
Subnet Mask..........................................................255.255.0.0
Default Gateway....................................................
Ethernet adapter Wireless Network Connection 2
Connection-specific DNS Suffix...................................
Description..........................................................Intel PRO/100 VE Network Connection
Physical Address....................................................00-18-DE-7A-24-54
DHCP Enabled.......................................................Yes
Autoconfiguration Enabled........................................Yes
Autoconfiguration IP Address......................................169.254.42.206
Default Gateway....................................................
Ethernet adapter Wireless Network Connection 3
Connection-specific DNS Suffix...................................
Description..........................................................Intel PRO/100 VE Network Connection
Physical Address....................................................00-16-36-98-E0-26
DHCP Enabled.......................................................Yes
Autoconfiguration Enabled........................................Yes
IP Address...........................................................0.0.0.0
Subnet Mask.........................................................0.0.0.0
Default Gateway....................................................
DHCP Server.........................................................255.255.255.255
And now PING isn't working again. Sheesh
Jack
Re: Connectivity issues
Posted: Fri Jul 18, 2008 10:46 am
by Darkstar
Looks like you are getting an auto IP config assigned or none at all, you are set to receive an IP from a DHCP server , is the DHCP assignment set in the router you are connecting to when you are trying to get on the internet? whats the setup?
you can also try turning off the "assign auto IP" function in the NIC properties
Re: Connectivity issues
Posted: Fri Jul 18, 2008 11:44 am
by unfaithfulsfan
I have many weak points but networking is REALLY my weak point, however, I'm slowly learning. His SOP for our clients' networks is to assign each node a static IP so he can utilize remote desktop. So I'm pretty sure this is set up the same way.I noticed when I ran IP config, no IP addresses that match this network showed up. Yesterday, it returned 192.168.1.6 which would make sense because my pc is 192.168.1.7. Now I'm confused, if I switched cables on my PC shouldn't I get a different IP address if that's the way this is set up?
Re: Connectivity issues
Posted: Fri Jul 18, 2008 1:41 pm
by Darkstar
192.168.1.6 is a wireless IP address, so it was likely assigned to the wireless NIC in the laptop, and a cable would have no effect on this address. I thought that maybe you were working on it at home and connecting through a home router. If he has settings for a static ip address in the NIC properties it could be causing problems.