Strange problem with Linksys WRT54G wireless router! can u help?
#1
Scooby Regular
Thread Starter
Join Date: Feb 2005
Location: From Your Worst Nightmare!
Posts: 1,362
Likes: 0
Received 0 Likes
on
0 Posts
Strange problem with Linksys WRT54G wireless router! can u help?
Having an odd problem with my Linksys router and can't figure it out.
I have DHCP enabled. My laptop connects to it fine both wirelessly and wired, It's given an IP address by the DHCP service no probs. My parents PC is also given an IP address successfully via the DHCP service.
However my desktop won't connect to it
It used to but not now.
Via command prompt typing ipconfig /all reveals the problems....
IP address is starts with something like 162(or 169).xxx.xxx.xxx which it shouldn't (can't remember the IP as i'm at work now)
Default gateway are similar, definitly not in the 192.168 IP range.
When I connect the cable windows says connected at 100mbps, green light is on on both NIC and Router for the port I'm using (tried all ports).
Thought perhaps it's the cable, so connected it into my Dlink DI-604 Router, IP assigned successfully and correctly. can access the Dlinks web admin service without any probs so cable appears to be ok and NIC appears to be working fine!!!
Anyone got any idea's what the problem is?! I've tried resetting the linksys router back to factory default, but same prob, all other comps connect ok but not my desktop!!
Help!?!?!?!
oh edited to add ipconfig /release followed by ipconfig /renew results in a error saying unable to contact DHCP server!
I have DHCP enabled. My laptop connects to it fine both wirelessly and wired, It's given an IP address by the DHCP service no probs. My parents PC is also given an IP address successfully via the DHCP service.
However my desktop won't connect to it
It used to but not now.
Via command prompt typing ipconfig /all reveals the problems....
IP address is starts with something like 162(or 169).xxx.xxx.xxx which it shouldn't (can't remember the IP as i'm at work now)
Default gateway are similar, definitly not in the 192.168 IP range.
When I connect the cable windows says connected at 100mbps, green light is on on both NIC and Router for the port I'm using (tried all ports).
Thought perhaps it's the cable, so connected it into my Dlink DI-604 Router, IP assigned successfully and correctly. can access the Dlinks web admin service without any probs so cable appears to be ok and NIC appears to be working fine!!!
Anyone got any idea's what the problem is?! I've tried resetting the linksys router back to factory default, but same prob, all other comps connect ok but not my desktop!!
Help!?!?!?!
oh edited to add ipconfig /release followed by ipconfig /renew results in a error saying unable to contact DHCP server!
#3
Scooby Regular
Thread Starter
Join Date: Feb 2005
Location: From Your Worst Nightmare!
Posts: 1,362
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by JackClark
Probably not the answer but I had my router set to only allow 3 users, when I tried connecting the forth the results were something like yours.
checked all the settings via one of the other computers, definitly not limited to x number of users. Get the same thing even when my desktop is the only thing linked to it.
Nothing for my desktop shows up in any of the routing tables either, it's as if it's not even connected ?!?!?!
#4
Scooby Regular
Join Date: Sep 1999
Location: Swindon, Wiltshire Xbox Gamertag: Gutgouger
Posts: 6,956
Likes: 0
Received 0 Likes
on
0 Posts
Are you sure the network card is working properly in the desktop?
Are there any little green lights flashing on the card in the back?
Are there any little green lights flashing on the card in the back?
#5
The linksysy software seems to "occasionally" forget the SSID settings and I've found that looking in there it'll have reverted to default and only a reboot would sort.
It has been better with XP SP2 and if it happens, I can use the "repair" option in the network connections window and it sorts it out.
Just realised your cabled to it so not the smae tihng at all! Sorry.
Can you assign a static address to it outside your DHCP scope?
That way it'll never fail trying to get one and default to the windows self assigned...
It has been better with XP SP2 and if it happens, I can use the "repair" option in the network connections window and it sorts it out.
Just realised your cabled to it so not the smae tihng at all! Sorry.
Can you assign a static address to it outside your DHCP scope?
That way it'll never fail trying to get one and default to the windows self assigned...
Last edited by HankScorpio; 20 July 2005 at 01:11 PM.
#7
Scooby Regular
Thread Starter
Join Date: Feb 2005
Location: From Your Worst Nightmare!
Posts: 1,362
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by GaryScoobNCBR
i think you maybe in luck, i had this problem with a machine the other day.
Try this..
goto cmd prompt and type
"netsh int reset" without the quotes
Try this..
goto cmd prompt and type
"netsh int reset" without the quotes
Trending Topics
#8
Try using a static address to establish the connection, if this doesn't work you've got a few things you'll need to try.
Have you tried a different cable anyway? have you tried a different port on the router? Do you have another network card you could try? Have you got latest firmware for Router?
good luck
Have you tried a different cable anyway? have you tried a different port on the router? Do you have another network card you could try? Have you got latest firmware for Router?
good luck
Thread
Thread Starter
Forum
Replies
Last Post