View Full Version : wtf network problmzz halp halp halp
Bad Waffle
August 27th, 2008, 11:38 PM
Ok, so i come home from school today. Sit down at my desk. Open up max, photoshop, and firefox. I go back to the firefox tab, no connection. Refresh, it instantly shows no page--like as if i wasnt connected to the internet.
I go into my connections, check my wireless--says -0 packets inc, 0 outgoing, so i try clicking repair. Immediately i get the screen
Windows could not finish repairing the problem because the following action cannot be completed:
Failed to query TCP/IP settings of the connection. Cannot proceed.
So i go fiddle around in those setting, restart, nadda. I'm getting slightly miffed, but in the meantime ive had time to open up new mombassa and get some ideas down. I aint gonna lie, its awesome.
But, no screenshots until my main computer gets workie workie. Har Har!
Kalub
August 27th, 2008, 11:46 PM
Open Command Prompt:
-If you have a Linksys Router:
-type "ping 192.168.1.1"
-if you have a Belkin Router:
-type "ping 192.168.2.1"
If those come back with replies type:
ping www.google.com (http://www.google.com)
If that comes back with replies then nothing is wrong (Probably not the case)
--------------------------------------------------------------------------
If your running wireless and can't ping your router:
-Make sure your connected, re-ping
If your hardwired and can't ping your router:
-Check Cables, restart router, re-ping
--------------------------------------------------------------------------
If your connected to your router make sure that its not your network card, if you can:
-Change out network cards
-Restart PC
Post back with what you come up with.
Amit
August 27th, 2008, 11:48 PM
What is he has a D-Link Router? Would you ping 192.168.0.1? I can't remember but I think that's it.
Kalub
August 27th, 2008, 11:53 PM
If you have a D-link router then kill yourself.... worthless things. :|
Bad Waffle
August 27th, 2008, 11:56 PM
Tells me destination host is unreachable. And oddly enough--it doesnt even recognize the lan ports built into the mobo--but it does recognize my wireless. It just cannot get through to my router with it.
FRain
August 27th, 2008, 11:56 PM
It also isnt always 192.168.2.1 it can also be 192.168.47.1 or 192.168.1.1 any number between 1 and (i think) 100 is different.
Kalub
August 28th, 2008, 12:06 AM
Tells me destination host is unreachable. And oddly enough--it doesnt even recognize the lan ports built into the mobo--but it does recognize my wireless. It just cannot get through to my router with it.
What kind of router/what did you ping?
Bad Waffle
August 28th, 2008, 12:24 AM
its not the bloody router, im obviously on the internet right now. I pinged the same thing on both my computers.
Kalub
August 28th, 2008, 12:27 AM
Its not the router I'm trying to diagnose.... I'm trying to see why you can't connect to it, or why its not letting you connect/use it. :|
Bad Waffle
August 28th, 2008, 12:31 AM
sorry, i've been pretty flustered ever since school started. I cry your pardon, sai.
It's a netgear WPN311, and a netgear router of unknown model
Kalub
August 28th, 2008, 12:35 AM
e:lemme find some info on those
tl;dr
1.Ping your router, replies goto #3
2.Check cables, re-ping, restart (powercycle) if fails goto #5
3.Ping a site that is always up, ie: google.
4.Contact ISP, most likely on their end
5. Most likely on your end, check the router on another computer, check hardware/settings
I need to go to bed, so I guess your on your own. :(
Kalub
August 28th, 2008, 12:42 AM
Ok, so.... the above posts mention your mobo not recognizing the LAN/Ethernet ports, did it before? Try a quick system restore to the closest date to you remembering them being recognized.
That or try a simple PC restart if you haven't already. Try a power cycle on router/modem, I'm just blurry on what you've tried ect.
Bad Waffle
August 28th, 2008, 12:42 AM
oi, thats stuff i've all done. Other than call the ISP, thats a bit stupid seeing as how its obviously something amiss in my computer.
Kalub
August 28th, 2008, 12:50 AM
Sounds like a driver/windows being fuctarded. If you can try a different NIC, maybe your onboard one just died. (Which is odd >_>)
Bad Waffle
August 28th, 2008, 01:09 AM
but how does that explain my mobo LAN not working?
Kalub
August 28th, 2008, 01:14 AM
I'm not really sure dude, all I can think of is that your mobo LAN died.... /outofideas
Rob Oplawar
August 28th, 2008, 04:53 PM
It may be that your mobo LAN device has been disabled, or the driver has gone away.
Go:
Control Panel > System > Hardware Tab > Device Manager (button)
Expand the Network adapters menu in the list. See if your ethernet port/net adapter/networking adapter/whatever is in that list, and if it is double click on it and see if it's configured properly.
Cortexian
August 28th, 2008, 05:21 PM
If you have a D-link router then kill yourself.... worthless things. :|
D-Link > Other Routers.
Anyways, did you take into consideration that it may be your ISP? I know that the mid-west was having some network issues yesterday.
Rob Oplawar
August 28th, 2008, 05:48 PM
he's already said multiple times that his other computer can access the internet through the same router just fine.
Timo
August 28th, 2008, 11:32 PM
but how does that explain my mobo LAN not working?
When I first got my computer I didn't install my motherboard's drivers (chipset :?) so the LAN plug didn't appear in windows. Had to go to a LAN to figure that one out :x
Rob Oplawar
August 31st, 2008, 01:17 PM
so am i to assume from your renewed presence on the forums that you fixed it?
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.