Date: Thu, 6 May 2004 14:08:24 +0900 From: Bull TORS <pwd8jmr22w@me.point.ne.jp> To: freebsd-questions@freebsd.org Cc: freebsd@pursued-with.net Subject: Re: Need Advice in SSH Message-ID: <200405061408.24580.pwd8jmr22w@me.point.ne.jp> In-Reply-To: <AD51BF8E-9F0F-11D8-8622-000A959CEE6A@pursued-with.net> References: <200405061032.19742.pwd8jmr22w@me.point.ne.jp> <200405061224.06064.pwd8jmr22w@me.point.ne.jp> <AD51BF8E-9F0F-11D8-8622-000A959CEE6A@pursued-with.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 06 May 2004 12:44, Kevin Stevens wrote: > On May 5, 2004, at 20:24, Bull TORS wrote: > > My laptop in the office (laptop1.mydomain.org) has a static internal > > network > > address 192.168.1.35 from my company's (companydomain.org) LAN Server. > > My laptop in my home has 192.168.1.x (I am not that sure if it changes > > a lot > > but I think not) as a DHCP client from my ISP (ispdomain.ne.jp). > > So I think both gets internal network addresses from their respective > > servers, > > one as a static client and the other as a dynamic client from different > > domains. Does this mean I can not use ssh from either both PC's? > > No, but you need more information. Some device on each end is > translating those non-routable private addresses to public ones usable > on the Internet. Almost certainly, at least one and probably both are > blocking inbound SSH connections by default. > > It is more likely that you can initiate outbound connections from your > company's network, and can configure your home network to permit > inbound connections. > > It is much less likely that you will be able to have your company > network configured to permit inbound connections initiated from your > home computer. > > In either case, you need more detailed information on the > configurations. Talk to the IT staff at your company and explain what > you're trying to do and ask if they permit outbound SSH sessions. At > your home, in my experience it's very uncommon for an ISP to provision > either DHCP or private addresses directly - it's more common for there > to be a local device in your home that is accomplishing that. But talk > to your ISP, it could be different in Japan. > > Properly speaking, this has little or nothing to do with FreeBSD, BTW, > it is general firewall, NAT and SSH information. Thanks for the response...I have tried to use ssh before but everytime I did a message always says "operation timed out"...and I could not know what went wrong...I have read the handbook and have found information using google before trying it and it seems that it was not working...I had to let it go for awhile or maybe gave up on it...but then it just keeps coming back to me because there are times when I really need to access my pc at home to administer it...That is why I posted my Email...just asking if it is really possible...Now, that I found out that it is going to take more reading and maybe try my settings in a different environment (if I am lucky)... Again, thanks for the reply...and my apologies for taking some of your minutes... Have a nice day guys... Bull TORS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405061408.24580.pwd8jmr22w>