Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2009

    Default Testing TCP Connectivity ... FAILED

    I don't know if the above error message is the cause of my problem, but ...

    I have two untangle boxes each has a static public IP on the external NIC, and each is attached to the main network switch. They each are passing internet traffice to network clients and everything seems to be working fine.

    I have 2 web servers on the network - I registered domain names on each and had each name associated with a specific static IP on an untangle box. I'll try to "diagram" it:

    (UT#1) (UT#2)
    -------\ /
    <Network Switch>

    Computers on the network access the internet through either UT#1 or UT#2.

    In both Untangle boxes I set port forwarding: Untangle #1 forwards: Destined Local, Protocol: TCP, Port: 80 to Web Server #1,
    and Untangle #2 forwards:
    Destined Local, Protocol: TCP, Port: 80 to Web Server #2.

    Server #1 seems to work fine for everyone (internal & external).

    Server #2 only works for machines that access the internet through UT#2 (I don't know about external).
    (But, a ping to server #2 from ANY machine returns the public IP of UT#2.)

    I have looked and it appears that everything is identical except Untangle #2 has more restrictive web filtering, Ad blocker, Phish blocker, and Attack blocker, and I tried turning off each of the blockers and it didn't seem to change anything.

    Then I did a connectivity test and I got: "Testing TCP Connectivity ... FAILED" (Testing DNS OK)

    Any ideas ?
    Is the connectivity causing the problem - but how can internet traffic be working with this error?

    Last edited by msaxby; 12-31-2010 at 11:30 AM.

  2. #2
    Untangle Ninja dwasserman's Avatar
    Join Date
    Jun 2008


    How many default gateway are in the lan?
    The world is divided into 10 kinds of people, who know binary and those not

  3. #3
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    San Carlos, CA


    the TCP connectivity test fails if it can't connect to port 80 to
    Not related to your issue but something to look into.

    the port forward on the second box fails because if the internal server isn't using the second box as a gateway the return packets won't go back to the second box so there is no way for the second box to "unmap" the packets and send them back to the original client.
    #2 topic
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

SEO by vBSEO 3.6.0 PL2