Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 10682 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Not Passing Traffic from UTM side of the Red Box

Kay Bowman

I am trying to set up the UTM to pass VNC traffic to the devices on the other side of the red box. I can VNC from the Red side to the main campus. When I do a tracert to a PC I only get to the router's IP address sitting just the other side of the red box. However; when I do a tracert to the printer I get to the printer. I can even open a web browser and get to the printer.



This thread was automatically locked due to age.
  • 0

    Hi, Kay, and welcome to the UTM Community!

    For those of us with a visual learning style, please supply a simple stick diagram.

    Do you learn anything from doing #1 in Rulz?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Firewall UTM -- REdbox--Router--Switch--Printer,Computer,Access Point

    Router Outside interface 10.10.10.242

    Router Inside interface 192.168.2.1

    Switch 192.168.2.2

    Printer 192.168.2.70

    Computer 192.168.2.8

    Access Point 192.168.2.227

     

    From My PC 10.10.10.102 - Can ping/tracert printer and Access Point

    C:\WINDOWS\system32>ping 192.168.2.70

    Pinging 192.168.2.70 with 32 bytes of data:
    Reply from 192.168.2.70: bytes=32 time=44ms TTL=253
    Reply from 192.168.2.70: bytes=32 time=44ms TTL=253
    Reply from 192.168.2.70: bytes=32 time=45ms TTL=253
    Reply from 192.168.2.70: bytes=32 time=45ms TTL=253

    Ping statistics for 192.168.2.70:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 45ms, Average = 44ms

    Tracing route to 192.168.2.70 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms firewall.cssbehavioral.org [10.10.10.100]
    2 48 ms 44 ms 44 ms 10.10.10.242
    3 44 ms 44 ms 44 ms 192.168.2.70

    Ping the computer

    C:\WINDOWS\system32>ping 192.168.2.8

    Pinging 192.168.2.8 with 32 bytes of data:
    Reply from 10.10.10.242: bytes=32 time=44ms TTL=127
    Reply from 10.10.10.242: bytes=32 time=44ms TTL=127
    Reply from 10.10.10.242: bytes=32 time=44ms TTL=127
    Reply from 10.10.10.242: bytes=32 time=48ms TTL=127

    Ping statistics for 192.168.2.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 48ms, Average = 45ms

    C:\WINDOWS\system32>tracert 192.168.2.8

    Tracing route to pc0400 [192.168.2.8]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms www.gateway.css [10.10.10.100]
    2 44 ms 53 ms 44 ms 10.10.10.242
    3 44 ms 46 ms 53 ms 10.10.10.242

     

    From UTM Ping printer

    PING 192.168.2.70 (192.168.2.70) from 10.10.10.100 br0: 56(84) bytes of data.

64 bytes from 192.168.2.70: icmp_seq=1 ttl=253 time=44.3 ms

64 bytes from 192.168.2.70: icmp_seq=2 ttl=253 time=44.1 ms

64 bytes from 192.168.2.70: icmp_seq=3 ttl=253 time=45.3 ms

64 bytes from 192.168.2.70: icmp_seq=4 ttl=253 time=43.9 ms

64 bytes from 192.168.2.70: icmp_seq=5 ttl=253 time=46.1 ms



--- 192.168.2.70 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 4005ms

rtt min/avg/max/mdev = 43.970/44.794/46.160/0.853 ms


    From UTM the computer

    PING 192.168.2.8 (192.168.2.8) from 10.10.10.100 br0: 56(84) bytes of data.

64 bytes from 10.10.10.242: icmp_seq=1 ttl=127 time=43.3 ms

64 bytes from 10.10.10.242: icmp_seq=2 ttl=127 time=44.8 ms

64 bytes from 10.10.10.242: icmp_seq=3 ttl=127 time=43.8 ms

64 bytes from 10.10.10.242: icmp_seq=4 ttl=127 time=43.1 ms

64 bytes from 10.10.10.242: icmp_seq=5 ttl=127 time=43.6 ms



--- 192.168.2.8 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 4005ms

rtt min/avg/max/mdev = 43.171/43.769/44.843/0.599 ms
  • 0 in reply to Kay Bowman

    I'm lost, Kay.  What function does the router perform?  What function does the RED perform?  what IPs are on those devices?  Maybe a picture of the Edit of the RED configuration would help, too.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Thanks Bob for getting back.

     

    The router IP inside is 192.168.2.1

    The router IP outside is 10.10.10.242

     

    Configuration for the Red


    reds7 (Internal_Red)
    RED ID: A3501B9A8C8CD2F
    Tunnel ID: 7
    Unlock Code: xxxxxxx
    UTM Hostname: 216.X.Y.66
    Uplink mode: DHCP
    Operation mode: Standard / Unified

     

    The router provides VLAN traffic between employee and vendor use.

  • 0 in reply to Kay Bowman

    Router:

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.2.8, timeout is 2 seconds:
    Packet sent with a source address of 10.10.10.242
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

     

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.10.10.100, timeout is 2 seconds:
    Packet sent with a source address of 192.168.2.1
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 44/44/44 ms

  • 0 in reply to Kay Bowman

    Bob,

     

    Thanks for the help.. It turns out it was my fault. I was doing a double NAT. I remove the NAT configurations on the router and all works ....

     

    Thanks again.

Unfiltered HTML