Access via static IP to internal server erratic / odd

Comments

5 comments

  • Avatar
    Firewalla

    How are you doing the RDP connection? via port forwarding from ATT to firewalla and firewalla to your RDP device? check that first. 

    0
    Comment actions Permalink
  • Avatar
    Christopher Hipskind

    Thanks for such a quick response!

    The ATT router is set up as Passthrough. The Firewall Purple is set up as a router.

    Under NAT setting on the FP, Source NAT is On. The Source Network / Local Network ip is the FP itself.

    No NAT Rules.

    No NAT Passthrough options selected.

    Port Forwarding is to the hostname of the internal server with a TCP port. Rule is Always, Allow: All Sources.

    UPnP is disabled.

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    The problem is unlikely at the network layer if some of your services works after the first one (especially the port/protocol is TCP). Are you able to read the RDP server logs? may be something there can give a better clue. 

     

    0
    Comment actions Permalink
  • Avatar
    Christopher Hipskind

    It's so odd ...

    So inside the office the RDP connection to the server never occurs. Users connect to it's internal IP or hostname with the port number without any issue.

    However, yes, I did take a look at MS eventviewer and didn't see anything weird there.

    I have a feeling it might be the ATT router. I am trying really hard not to contact their support because it's usually a pain in the neck until I get someone decent.

    I listed the changes I made to the ATT router to set it up as passthrough. If I send you a text file with the settings, can you take a quick look and see if I missed something?

    Thanks again!

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    Since your connections are getting through, your best bet is look at the logs to see what is rejecting your connection. (I do remember Microsoft also has its own firewall, not sure if it is an issue or not) 

    Try a different port you used publicly, may be something there that the ISP may be filtering. 

    Sorry, we can't help with ATT configurations. 

    0
    Comment actions Permalink

Please sign in to leave a comment.