NATD Port Forwarding question

2004-07-04 Thread Jon Kurjakovich
Hi there,

I am currently using FreeBSD 4.8-RELEASE. I do plan on upgrading to
5.2-CURRENT shortly but I know people who are using 5.2-CURRENT and are
experiencing the same problem as me. If this email is not appropriate in
this mailing list, could you please forward me to the correct one. Thank
you.

My problem: I am trying to use NATD to forward packets to machines on
the internal network using the redirect_port command. I am specifically
trying to connect to a Terminal Server on a Windows 2000 machine. It
never seems to work for me. I am running natd using the following
command: natd -f /etc/natd.conf with the following options in my
natd.conf file.

interface tun0
same_ports yes
use_sockets yes
unregistered_only
redirect_port tcp 192.168.1.2:3389 3389

When I create an SSH tunnel using putty, that works fine. It is only
when I try and use natd w/ port-forwarding that it doesn't work. I
configure an extremely open firewall to ensure it is not my firewall
causing the problems. The commands I use are:

/sbin/ipfw -f flush
/sbin/ipfw add 50 divert natd all from any to any via tun0
/sbin/ipfw add pass all from any to any

If anybody could shine any light on this problem for me - it'd be
greatly appreciated. I have been trying to resolve the problem
on-and-off for months now to no avail. I finally decided I should try
the mailing list.

Thanks.

Regards,
Jon


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: NATD Port Forwarding question

2004-07-04 Thread Micheal Patterson
Is the system configured to accept remote desktop requests? Windows XP has
it disabled by default.

--

Micheal Patterson
TSG Network Administration
405-917-0600

Confidentiality Notice:  This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.


- Original Message - 
From: Jon Kurjakovich [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, July 04, 2004 3:57 AM
Subject: NATD Port Forwarding question


 Hi there,

 I am currently using FreeBSD 4.8-RELEASE. I do plan on upgrading to
 5.2-CURRENT shortly but I know people who are using 5.2-CURRENT and are
 experiencing the same problem as me. If this email is not appropriate in
 this mailing list, could you please forward me to the correct one. Thank
 you.

 My problem: I am trying to use NATD to forward packets to machines on
 the internal network using the redirect_port command. I am specifically
 trying to connect to a Terminal Server on a Windows 2000 machine. It
 never seems to work for me. I am running natd using the following
 command: natd -f /etc/natd.conf with the following options in my
 natd.conf file.

 interface tun0
 same_ports yes
 use_sockets yes
 unregistered_only
 redirect_port tcp 192.168.1.2:3389 3389

 When I create an SSH tunnel using putty, that works fine. It is only
 when I try and use natd w/ port-forwarding that it doesn't work. I
 configure an extremely open firewall to ensure it is not my firewall
 causing the problems. The commands I use are:

 /sbin/ipfw -f flush
 /sbin/ipfw add 50 divert natd all from any to any via tun0
 /sbin/ipfw add pass all from any to any

 If anybody could shine any light on this problem for me - it'd be
 greatly appreciated. I have been trying to resolve the problem
 on-and-off for months now to no avail. I finally decided I should try
 the mailing list.

 Thanks.

 Regards,
 Jon


 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
[EMAIL PROTECTED]


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: NATD Port Forwarding question

2004-07-04 Thread Jon Kurjakovich
Yes. It is a Windows 2000 Server machine that I can connect to both on
the local network and via an SSH tunnel. It is simply to do with natd's
port forwarding. I also cannot use port forwarding to access any other
services on the 2000 Server box such as telnet or ftp for example.

Any help is greatly appreciated.

Rgds,
Jon

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Micheal
Patterson
Sent: Sunday, 4 July 2004 8:12 PM
To: Jon Kurjakovich; [EMAIL PROTECTED]
Subject: Re: NATD Port Forwarding question


Is the system configured to accept remote desktop requests? Windows XP
has it disabled by default.

--

Micheal Patterson
TSG Network Administration
405-917-0600

Confidentiality Notice:  This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.


- Original Message - 
From: Jon Kurjakovich [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, July 04, 2004 3:57 AM
Subject: NATD Port Forwarding question


 Hi there,

 I am currently using FreeBSD 4.8-RELEASE. I do plan on upgrading to 
 5.2-CURRENT shortly but I know people who are using 5.2-CURRENT and 
 are experiencing the same problem as me. If this email is not 
 appropriate in this mailing list, could you please forward me to the 
 correct one. Thank you.

 My problem: I am trying to use NATD to forward packets to machines on 
 the internal network using the redirect_port command. I am 
 specifically trying to connect to a Terminal Server on a Windows 2000 
 machine. It never seems to work for me. I am running natd using the 
 following
 command: natd -f /etc/natd.conf with the following options in my
 natd.conf file.

 interface tun0
 same_ports yes
 use_sockets yes
 unregistered_only
 redirect_port tcp 192.168.1.2:3389 3389

 When I create an SSH tunnel using putty, that works fine. It is only 
 when I try and use natd w/ port-forwarding that it doesn't work. I 
 configure an extremely open firewall to ensure it is not my firewall 
 causing the problems. The commands I use are:

 /sbin/ipfw -f flush
 /sbin/ipfw add 50 divert natd all from any to any via tun0 /sbin/ipfw 
 add pass all from any to any

 If anybody could shine any light on this problem for me - it'd be 
 greatly appreciated. I have been trying to resolve the problem 
 on-and-off for months now to no avail. I finally decided I should try 
 the mailing list.

 Thanks.

 Regards,
 Jon


 ___
 [EMAIL PROTECTED] mailing list 
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
[EMAIL PROTECTED]


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: NATD Port Forwarding question

2004-07-04 Thread andrew clarke
On Sun, Jul 04, 2004 at 06:57:16PM +1000, Jon Kurjakovich wrote:

 My problem: I am trying to use NATD to forward packets to machines on
 the internal network using the redirect_port command.

I don't have a solution to your problem with natd, however net/rinetd
(from ports) might be a good enough workaround if all else fails.

Port:   rinetd-0.62
Path:   /usr/ports/net/rinetd
Info:   A simple TCP port redirector
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]