Reply
kaweahnet
Posts: 4
Registered: ‎09-28-2006

Website works wirelessly - but not wired through a WRK54G

Yes, you read this correctly ... my client has a website that works wirelessly  but NOT when plugged into the WRK54G. 
 
So far, all my work has been done remotely over the phone because her remote desktop does not appear to be functioning correctly either. 
 
It is an MLS website with a saved query on it.  All other websites appear to be working correctly, but when she tries to access this saved query it just times out.  Like I said, unplug the wire - turn on the wireless, it all works great.  Both connections are firewalled through XP SP2 firewall.
 
I'm trying to get some ideas before I drive out to her house and begin charging her my hourly rate to run Wireshark traces to find out what is going on.
 
Any ideas?
Posts: 125
Registered: ‎07-13-2006

Re: Website works wirelessly - but not wired through a WRK54G

Hi,

May I ask what is the firmware version of the wrk54g router?  Are you sure that the wireless computer is connected to his/her wireless network which is owned by her router?

lina1
Posts: 123
Registered: ‎08-12-2007

Re: Website works wirelessly - but not wired through a WRK54G


check the ip on LAN---there should be any static ip on pc---also uncheck the LAN settings in IE
Corleone
Posts: 2,785
Registered: ‎09-07-2006

Re: Website works wirelessly - but not wired through a WRK54G

hi...i agree to charrie21 that the wireless computer might be connected to one of your neighbour's network while accessing the website...verify the same and revert with the results ..
kaweahnet
Posts: 4
Registered: ‎09-28-2006

Re: Website works wirelessly - but not wired through a WRK54G

[ Edited ]
Thank you for your responses!  I have now visited the customer's location and this is absolutly insane.  Here is what I know.
 
The router is a WRK54G v2 with latest firmware (according to linksys) of 1.00.1
 
They are connecting through an MLS website at http://maxebrdi.fnismls.com/Paragon.  The login works fine, and most browsing works fine until they try to pull down this particluar saved listing.  It should take about 15-20 seconds to pull this listing down when successful ... but during a failure it is just a white page, three to five green dots on the IE progress bar.  Customer has waited up to 20 minutes and it never does anything.
 
When connected through the router wirelessly using WEP this particluar download described above works just fine.  I know that they are using the local router by checking the DHCP lease on the router vs the IP address & MAC on the wireless NIC.
 
When wired thorugh the router - sure enough, it fails.  I did some network traces during the failure to see where it is getting torn down.  It appears the client is doing a FIN, ACK to the server after getting some payload about the page being unavailable, then it does a RST, ACK and eventually a RST. 
 
I did come up with a work around temporarily though.  When wired through the router I have them VPN into my home office (Microsoft VPN).  Now the client machine is encrypting the traffic through the router and the page works just fine.  As long as I can hide the payload from the router it works just great.
 
Furthermore, when they take their computer off-site and put it on another individuals network (wired) it all works fine.  Everything is pointing to this router.
 
Here is the part of the network trace where it appears to get torn down:
  • 189 10.818509 205.240.85.41 192.168.1.104 TCP http > 1240 [ACK] Seq=35153 Ack=2977 Win=65380 Len=0
  • 190 10.821519 205.240.85.41 192.168.1.104 TCP [TCP segment of a reassembled PDU]
  • 191 10.822522 192.168.1.104 205.240.85.41 TCP 1240 > http [FIN, ACK] Seq=2977 Ack=35689 Win=65535 Len=0
  • 192 10.823525 205.240.85.41 192.168.1.104 TCP [TCP segment of a reassembled PDU]
  • 193 10.823525 192.168.1.104 205.240.85.41 TCP 1240 > http [RST, ACK] Seq=2978 Ack=36225 Win=0 Len=0
  • 194 10.824528 192.168.1.104 205.240.85.41 TCP 1241 > http [SYN] Seq=0 Len=0 MSS=1460
  • 195 10.827538 205.240.85.41 192.168.1.104 TCP [TCP segment of a reassembled PDU]
  • 196 10.827538 192.168.1.104 205.240.85.41 TCP 1240 > http [RST] Seq=2977 Len=0
  • 197 10.889736 192.168.1.104 205.240.85.41 TCP 1239 > http [ACK] Seq=3115 Ack=17843 Win=65231 Len=0

Obviously, the easy solution is to find an older router (WRT54G) and replace the router at a cost of $49.  But I am really stumped here ... and I look like a chump because I sold them the WRK54G router.

Is there a way to get this information to a Linksys Engineer to find out what is going on?

 

 
 


Message Edited by kaweahnet on 11-07-2007 07:27 AM
-OTAKUS_06-
Posts: 290
Registered: ‎07-11-2006

Re: Website works wirelessly - but not wired through a WRK54G

Have you tried forwarding those ports mentioned on the logs? or maybe adjusting the MTU size on the router to 1300?

"You tried your best and you failed miserably! "
kaweahnet
Posts: 4
Registered: ‎09-28-2006

Re: Website works wirelessly - but not wired through a WRK54G

Thx for the advice.
 
Ports wouldn't be required to be forwarded, because it works fine wirelessly.  Good advice on the MTU but I already tried it; reduced it all the way down to the minimum (576 I think). 
 
Just got done in CHAT with Linksys support and it appears that there are high bandwidth issues with this particular version of the router.  They are going to have me testing some beta firmware for them to see if it resolves the issue.
 
So far, I'm pretty satisfied with support!  Go Linksys!  :smileyvery-happy: