From owner-freebsd-questions Wed May 17 13:11: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from chi1.nucleusconsulting.com (chi1.nucleusconsulting.com [207.250.168.11]) by hub.freebsd.org (Postfix) with ESMTP id B57E837BD64 for ; Wed, 17 May 2000 13:10:51 -0700 (PDT) (envelope-from parrothd@midwest.net) Received: from zippy2 (labntserver1.nucleusconsulting.com [207.250.168.3]) by chi1.nucleusconsulting.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id KRCNTHC9; Wed, 17 May 2000 15:07:57 -0500 Message-Id: <3.0.5.32.20000518150945.013d11b0@midwest.net> X-Sender: parrothd@midwest.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 18 May 2000 15:09:45 -0500 To: Mohsin Rahman , FreeBSD Questions From: "Jonathan E. Lyons" Subject: Re: pcAnywhere and NATD/ipfw In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Use VNC instead of PcAnywhere.. :) http://www.uk.research.att.com/vnc/ At 04:05 PM 5/17/00 -0400, Mohsin Rahman wrote: >After reading the Questions archives and FreeBSDDiary.org, I >setup a FreeBSD-3.2 box (test) with two NICs, rl0 (dedicated IP) >and fxp0 for my internal (10.0.0.0) network. > >I have NATD and Firewall=OPEN working. Initially, I went with >natd's redirect_port option, but realized it wasnt working for >me. So I installed "rinetd" from the ports collection and >redirected ports 22, 5631, 5632 and 65301 to a Win98 box on >my private network (pc1/10.0.0.5). > >Just to make sure it was working, I also setup a Sambar Web >server on the Win98 (10.0.0.5) box and accessed it from over >the internet. I got this: > >bash-2.03# sockstat |grep rinetd >root rinetd 392 4 tcp aa.bb.cc.dd.22 *.* >root rinetd 392 5 tcp aa.bb.cc.dd.80 *.* >root rinetd 392 6 tcp aa.bb.cc.dd.5631 *.* >root rinetd 392 7 tcp aa.bb.cc.dd.5632 *.* >root rinetd 392 11 tcp aa.bb.cc.dd.80 136.183.5.110.1093 >root rinetd 392 12 tcp 10.0.0.1.1073 10.0.0.5.80 > >and I was able to pull up some test pages on the Win98 (10.0.0.5) >box. Great!! This part is done. Then I tried pcAnywhere > >and got: > >bash-2.03# sockstat |grep rinetd >root rinetd 392 4 tcp aa.bb.cc.dd.22 *.* >root rinetd 392 5 tcp aa.bb.cc.dd.80 *.* >root rinetd 392 6 tcp aa.bb.cc.dd.5631 *.* >root rinetd 392 7 tcp aa.bb.cc.dd.5632 *.* > >basically no connection and pcAnywhere times out waiting for a >host to answer. When I initiate the pcAnywhere connection, I get >this in /var/log/messages > >May 17 15:34:26 test /kernel: Connection attempt to UDP aa.bb.cc.dd:22 >from 136.183.5.110:1202 > >May 17 15:39:12 test /kernel: Connection attempt to UDP aa.bb.cc.dd:5632 >from 136.183.5.110:1205 > >I also added this to /etc/serives to see if it made any difference: > >pc-anywhere 5631/tcp >pc-anywhere 5631/udp >pc-anywhere 5632/tcp >pc-anywhere 5632/udp >pc-anywhere 56301/tcp >pc-anywhere 56301/udp > >I believe it has to do something with port 22 and 5632 combination. >Does anyone know how I go about fixing this. Thanks! > >Mohsin AbdulRahman >MTech@BuffNET.Net > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > > Jonathan E. Lyons Nucleus Consulting parrothd@midwest.net www.nucleusconsulting.com ICQ # 14226912 A+, MCSE, CCNA, FreeBSD! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message