[ previous ] [ next ] [ threads ]
 From:  Frank Bello <fbello at bytcorp dot com>
 To:  Daniel Jokinen <daniel dot jokinen at linford dot se>, "m0n0wall at lists dot m0n0 dot ch" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: Port Forwarding problem on 2023
 Date:  Wed, 24 Apr 2013 17:12:54 +0000
Never mind!
Dan, thanks for the input.
I went back to the guy that administers the unix server...

He updated the IP configuration to work in the new environment that we setup and he 'forgot' to set
the gateway address.
So the M0n0wall was working correctly but the replies could never get back out.

User error. ;-))

Thanks all


-----Original Message-----
From: Daniel Jokinen [mailto:daniel dot jokinen at linford dot se] 
Sent: Wednesday, April 24, 2013 2:25 AM
To: m0n0wall at lists dot m0n0 dot ch
Subject: [m0n0wall] SV: Port Forwarding problem on 2023

Hi Frank,

Usually whenever I get these kinda problems I delete the rule and set it again, which always seems
to work. Make sure you use the "auto add firewall rule" when creating the NAT rule, failure  to do
so can cause problems I know from experience.

However, it that doesn't work I'd start looking in the other end first. Does port 2023 work
internally? Is there a firewall in use at the unix server side? Can you access canyouseeme.org from
the unix server and see if it actually does work and there's something else all together?

 /Daniel Jokinen

-----Ursprungligt meddelande-----
Från: Frank Bello [mailto:fbello at bytcorp dot com]
Skickat: den 24 april 2013 03:16
Till: m0n0wall at lists dot m0n0 dot ch
Ämne: [m0n0wall] Port Forwarding problem on 2023

I've been testing the M0n0wall appliance in an ESX 3i host and have been very pleased with it.
However I wonder if someone can help me find out how come a port/NAT forwarding rule that I'm trying
to set for port 2023 is not working.

The rule allows access to the outside TELNET clients to an internal UNIX server which is listening
for TELNET connections on port 2023

I have setup forwarding rules for RDP on 3389 and for VMWARE client management on SSL and other
private ports and it works perfectly. However when I tell it to forward 2023 it does not. And only
in that rule.

I have also tried to create another rule where the external port 23 will be forwarded to the
internal 2023, but that does not work neither

Following are the pages from my setup. Any help ? thanks in advance.

F. Bello

Firewall: NAT: Inbound

InboundServer NAT1:1Outbound
  If Proto Ext. port range NAT IP Int. port range Description  WAN  TCP  3389  3389 
RDP Service  WAN  TCP/UDP  443 (HTTPS)  443 (HTTPS)  VMWARE SSL  WAN  TCP/UDP  902 -
903  902 - 903  VMWARE  WAN  TCP/UDP  2023  2023  UNIX Server Access

Firewall: Rules

    Proto Source Port Destination Port Description
   TCP  *  *  3389  NAT RDP Service
    TCP/UDP  *  *  902 - 903  NAT VMWARE
    TCP/UDP  *  *  443 (HTTPS)  NAT VMWARE SSL
    TCP/UDP  *  *  2023  NAT

To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch