asked on

Cannot connect to a specific host using Linksys E1200

I just bought a new Linksys E1200 Wi-Fi router. For the most part, it works fine. I normally connect to several remote hosts on port 22 via ssh, WinSCP and Putty. I can connect to all these computer w/o problem ... except to one specific host! I have several computers on my home LAN and none of them can connect to this host. They can connect to all the others, but not this one. Putty gives me "Network Error. Connection timed out." ssh gives me, "ssh: connect to host port 22: Connection timed out." I know it has something to do with the router because when I put the old D-Link back in, all computers can then connect to this host. I tested this with more than one router and they all let me connect to that remote most, except the new Linksys.

The Linksys has a diagnostic page. Pinging the host/IP (96.11.168.98) from the Linksys gives 100% data loss. Traceroute from the Linksys gives "request timed out."

I have been working with and configuring network devices, home and business, fora long time and this is the first time I have ever seen a router refuse to connect to a specific address w/o being in some kind of block list. If this router has such a list, I have not found it. I've disabled the Linksys firewall.

I have absolutely no clue what could be wrong. Does anyone have an idea? I'm not going to waste much time on this. If I can't get it working I'll return the device.

THX

phoenix5ire

You have verified if port 22 is open on the host that can't be connected?

Make sure the host has Internet connection and do this test on the problematic host: open up command prompt, type:
telnet lrd.avss.ucsb.edu 22

If Port 22 is open, you will see a line containing SSH. If not, you will get a 'no connect' message.

Hope this helps.

Mark

ASKER

> You have verified if port 22 is open on the host that can't be connected?

Yes, it's open because, as I stated, if I use a different router I connect OK. Also, I can connect to one of the other hosts, then connect to the "problematic" host via ssh. You can try it yourself. I've put the IP in my original message.

> do this test on the problematic host ...

That test works fine:

$ telnet lrd.avss.ucsb.edu 22
Trying 128.111.147.200...
Connected to lrd.avss.ucsb.edu.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.4p1 FreeBSD-20100308
^]
telnet> quit
Connection closed.

I can also connect from the remote "problematic" host to any host. I just cannot connect from this Linksys router to that host.

I also have this router port-forwarding to a linux host on the local LAN. I can get to this host from any remote host, but not from "problematic" host. Again, that specific host appears to be blocked at the router. Example:

telnet 76.181.71.79 20028

This works from any host (doubtless including yours). From IP 64.129.23.95 I get:

$ telnet 76.181.71.79 20028
Trying 76.181.71.79...
Connected to 76.181.71.79.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.0
^]
telnet> quit
Connection closed.

but from problem IP 96.11.168.98. I get:

$ telnet 76.181.71.79 20028
Trying 76.181.71.79...

forever ...

Whereas your test telnet worked just fine. Again, keep in mind, this all works fine with at least two other routers I just tested. What do you think?

phoenix5ire

*hmmm, interesting one. I did tried both of your IPs and was able to establish a telnet session w/o any problem on port 22. This verifies port 22 is open on your .98 host.

One quick thing to try is clear your arp cache from one of your host and try telnet again to the problematic host:
netsh interface ip delete arpcache

I'll do more brainstorming at the office in the morning.

phoenix5ire

It's apparent the Linksys E1200 is the problem and it looks like you've done some extensive testing already, here's what I would do: (one step at a time and test, so you can narrow the problem)
1) Check for a new firmware on the Linksys and apply as necessary - then test
2) Update driver on the NIC of problematic host (PC) - then test
3) Change out the NIC on the problematic host (PC) with one from your other machines that works and see if that makes any difference. -then test.

Hope this helps.

Mark

ASKER

> 1) Check for a new firmware on the Linksys and apply as necessary - then test

Actually, I would like to try the new firmware idea. I attempted this yesterday. Ufortunately, when I go to the Linksys site for downloading firmware: http://support.linksys.com/en-us/support/routers/E1200/download, all I can seem to download is a license agreement PDF no matter what I click on! If you want to try one more thing, see if you can find a link on that page that would actually let me download firmware.

Othere than the firmware possibility, I appreciate your excellent suggestions, but changing the card in the problematic host (Linux) ... and there isn't a specific new driver for that, is way too much work for a $50 router -- and does not have a high probability of working since all other computers and all other routers can get to it w/o problem.

If I could try the firmware idea, I would. Otherwise, this device goes back to the store today.

phoenix5ire

I got the firmware for you, see URL. It's the latest from Linksys:
Firmware
04/16/2013
Ver.2.0.05 (Build 2)

Attaches is also the Install instructions.
Router-Firmware-Upgrade-Instruct.pdf

ASKER CERTIFIED SOLUTION

Mark

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

phoenix5ire

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Mark

ASKER

I've requested that this question be closed as follows:

Accepted answer: 0 points for jmarkfoley's comment #a39233244
Assisted answer: 500 points for phoenix5ire's comment #a39242065

for the following reason:

I figured it out.

Mark

ASKER

I'll try re-closing the question.

Mark

ASKER

wrong button

Mark

ASKER

I figured it out.