Page 1 of 2 12 LastLast
Results 1 to 10 of 14
  1. #1
    Untanglit
    Join Date
    Sep 2010
    Posts
    28

    Default Internal DNS issues

    Since i updated from 9.0.1 Build 4 -> 9.0.2 Build 1, i have been unable to view my internally host webpage from with in my network... i can view it from my blackberry but when i try and view it from a machine on the same LAN all i get is a "untangle server not found" error...

    Dmorris has stated "hairpin port forwards work fine in 9.0.2 - I just checked."

    The port 80 forward will work upto the point just before the UVM fully loads after a reboot.

    the box has been running for over a year.

    I have done a fresh load and restored settings, I do realize the potential for the backup settings causing this issue. I just don't have the time right now to re-configure from scratch.

    Everything else appears to work perfectly.

    Thanks in advance for any advice.

  2. #2
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    25,093

    Default

    Please post a screen shot of your port forward.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  3. #3
    Untanglit
    Join Date
    Sep 2010
    Posts
    28

    Default

    Here is the screen, just a basic forward.

  4. #4
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    25,093

    Default

    Please switch the forward to advanced mode and post that one, those basic forward don't tell me what's really going on.

    I suspect that rule is based on "destined local" and as such you're trying to access port 80 on Untangle's "internal" which isn't possible. That port is locked to internal administration.

    You need to not use "destined local" and use "destination address" and manually specify the appropriate WAN address.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  5. #5
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    other tips:

    http://wiki.untangle.com/index.php/P...shooting_Guide

    tcpdump could give some clues, and just tests with telnet.
    Also check your NAT setting in config->networking->advanced.
    Is "Only NAT WAN traffic" enabled?
    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 support@untangle.com

  6. #6
    Untanglit
    Join Date
    Sep 2010
    Posts
    28

    Default

    Originally yes is was "Destined local" i have switch it to the below screen.

    it used to work...

    Is "Only NAT WAN traffic" enabled? Yep it is.

  7. #7
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    What does DNS have to do with this?
    Are you testing with IPs or hostnames? Does it work with the IP? How about the hostname? What does the IP lookup to?

    Follow the troubleshooting guide and post your results.

    You can also try checking "Port Forwards override administration."
    I'd only suggest this if you have a keyboard and monitor hooked up.
    Last edited by dmorris; 08-13-2011 at 12:07 PM.
    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 support@untangle.com

  8. #8
    Untanglit
    Join Date
    Sep 2010
    Posts
    28

    Default

    Forgot the screen...

    If I enter the internal IP of the machine hosting the site i get the site, if I enter the domain www.example.com I get the untangle error. only inside the LAN.

  9. #9
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    hmm.. I wonder if this is different because its port 80. I tested with 1234...
    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 support@untangle.com

  10. #10
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    I think that is the case. Its trying to display the blockpage.
    I will look into a fix for the next build.
    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 support@untangle.com

Page 1 of 2 12 LastLast

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