This is the mail archive of the
mailing list for the Cygwin project.
Re: Telnet / SSH connection timeout on LAN
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Wed, 8 Jul 2015 15:06:43 -0600
- Subject: Re: Telnet / SSH connection timeout on LAN
- Authentication-results: sourceware.org; auth=none
- References: <1436142936994-119480 dot post at n5 dot nabble dot com> <87113420 dot 20150706182615 at yandex dot ru> <CAOY0qXTuXahbGrw280vUecD3BpV4nxfXNPiYZ3UE-bZg+qfXEA at mail dot gmail dot com>
On Jul 6, 2015, at 1:03 PM, Joseph B <email@example.com> wrote:
> LAN Adapter
> IP: 192.168.0.2 (static)
> Subnet Mask: 255.255.255.0
> no DNS server
> Wifi Adapter
> 192.168.254.18 (dynamic)
> gateway: 192.168.254.254
Mask 255.255.255.0 means the first three octets are the network number, and the last is the station number. Thus, your two machines are on *completely different networks*, at a logical level. Your OS is sending the packets from one to your home router, and your router doubtless has no idea that it is supposed to be routing between two different 192.168 networks.
Solution: Put the static machine on 192.168.254.x.
Look at your DHCP serverâs configuration to find a safe value for x.
And since you said you have no idea what youâre doing, I will tell you that your LANâs DHCP server is almost certainly a feature on your home router. DHCP configuration is different for every router.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple