Problem with ethernet on WAG54g

Macca

Macca

Macca

Associate
Joined
28 Sep 2004
Posts
2,019
Location
Wanaka
Well lately, my WAG54g has been acting weird. My connection is wired into it and two others are wireless. Now the wireless ones are always working but my wired keeps acting up, the light flashes saying it's connected on router then on pc says unplugged,connecting then eventually stops workings or gives me the other problem i've had which is it giving me an invalid ip.

It keeps giving me this ip; 169.245.68.149 and says limited or no connectivity. Now i don't understand why as the internal ips are 192.168.1.1 and up.

Could this be my router or my pc as i've tried two different ones on pc, problems vary from each port limited or no connectivity on one, and flashes on other.

If anyone has any ideas that would be good, gonna email linksys also see what they say, might need to RMA it?

Macca.
 
Macca said:
Numerous times, no offence seems like a silly question to ask me.
Click to expand...

You have to bear in mind the level of networking knowledge some people on the forums have, so no, that wasn't a silly question to ask as you hadn't said in your post that you had already tried it.

You're getting the 169.254 address because Windows can't talk to the DHCP server in the router so it trys to be helpful and assigns itself an IP address.

Have you tried different network cables, different ports in the router, different network card in the PC? Or am I offending you my offering such silly advise?
 
An address in the form of 169.254.X.X it is whats known as an Automatic private ip address, it is used when windows cannot obtain an address using DHCP or if no static address has been configured.

It allows clients on the same subnet to talk to each other in the event no DHCP server is avaliable.

But you already knew that didnt you.
 
Burbleflop said:
You have to bear in mind the level of networking knowledge some people on the forums have, so no, that wasn't a silly question to ask as you hadn't said in your post that you had already tried it.

You're getting the 169.254 address because Windows can't talk to the DHCP server in the router so it trys to be helpful and assigns itself an IP address.

Have you tried different network cables, different ports in the router, different network card in the PC? Or am I offending you my offering such silly advise?
Click to expand...
Yes i realise that, i don't know a lot myself either so i apoligise for that and i had just got up :p

Ok, what you are all saying sounds about right, but the wireless part is having no problem with this it's just the wired.
 
crashuk said:
give it a static ip and see, maybe your network cable has degraded.
Click to expand...

What difference will giving it a static IP make? If the cable (or whatever) is dead enough that you can't get an IP address from the DHCP server then even assigning it a static isn't going to give you working internet access.
 
It will work for periods of time then randomly do this, i've tried with and without a firewall. I've also put the cable into a different port. I've tried giving it a specific IP from the router and seeing if it connects that doesn't work neither.
 
crashuk said:
then it might be *** cable or your network card then.
Click to expand...
What can cause the cable to become like this? Also i've tried to cards well (onboard) Nvidia and Realtek ones.
 
Too much stress on the RJ45 plugs van cause cables to come loose in the crimp, poor crimping originally, overbending of the cable (the individual conductors are solid and can break inside the cable) direct pressure on the cable (being stood on etc) can break the conductors.
Your symptoms sound like one of the strands inside the cable has broken and is intermitantly making contact, hence the variable nature of your connection
 
Musashi said:
Too much stress on the RJ45 plugs van cause cables to come loose in the crimp, poor crimping originally, overbending of the cable (the individual conductors are solid and can break inside the cable) direct pressure on the cable (being stood on etc) can break the conductors.
Your symptoms sound like one of the strands inside the cable has broken and is intermitantly making contact, hence the variable nature of your connection
Click to expand...
Could heat cause this too?
 
It is unlikely that heat (caused by weather) would damage your cable. Just out of curiosity, how long is the cable ? Did it have the ends crimped on or did you crimp them on yourself? Is it easy to replace the cable ?
 
I have a WAG54G which does this exact same thing, the wired connections start working if you leave them plugged in for a couple of hours and then renew.

I havent ever found a resolution. Its not a cable thing, its the router.
 
Jez said:
I have a WAG54G which does this exact same thing, the wired connections start working if you leave them plugged in for a couple of hours and then renew.

I havent ever found a resolution. Its not a cable thing, its the router.
Click to expand...
Well that doesn't sound good, it's never done this before til few weeks ago when i got back from Canada. When i mean heat i mean constant heat from a radiator not the weather. The cable isn't very long, metre or so.
 
Musashi said:
Sounds like RMA time. This is not good. But I would try replacing the cable frst.
Click to expand...
Ok thanks everyone, i'll see how things go after i replace the cable.
 
You must log in or register to reply here.
Back
Top Bottom