logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
IP  
#1 Posted : Monday, May 1, 2017 10:17:16 AM(UTC)
IP


Rank: Newbie

Joined: 9/7/2013(UTC)
Posts: 12
Location: Australia

okay, here's a head scratcher.

Got a sub domain that points to a static IP (my static IP). It can access and work externally from any device via IP:8040 and (subdomain):8040

For whatever reason, it will not resolve internally on my ScreenConnect server. Local/internal IP:8040 is the only way it works.

I have correct port forwarding rules set in the router to the SC Server/Host (which also has a static IP behind the NAT)
The router port forwarding is working, as I can access the SC host externally.

Seems to be something on this Windows 7 pro box that's running the SC host that is stopping everything other than it's internal static IP:8040

(tried Win 7firewall off, different DNS's, still failing)

Could the router being preventing the outgoing requests to a DNS and back to itself again?

The problem is no support invitations can be sent because the link generated is my internal/local IP:8040. Competely useless.

Any light on the mystery would be greatly appreciated.

Thank you.

Edited by user Monday, May 1, 2017 3:28:59 PM(UTC)  | Reason: Not specified

IP  
#2 Posted : Monday, May 1, 2017 5:20:13 PM(UTC)
IP


Rank: Newbie

Joined: 9/7/2013(UTC)
Posts: 12
Location: Australia

Possibly SOLVED: I edited the HOSTS file on the SC Host/Server to resolve to a website address.
Packet Rewriting has been an issue on my router I suspect. Will see how this works in the meantime.


HOW?

Open Hosts File (in Windows)
Open Notepad in Administrator Mode and browse to C:\windows\system32\drivers\etc\hosts
Open the Hosts file

add a line and the bottom
your local IP website
Example: 192.168.1.35 randomwebsite.com

Save (Save As Type) All Files

Restart Broswer and try again. Should now work.
MannyTC  
#3 Posted : Monday, May 1, 2017 6:13:35 PM(UTC)
MannyTC


Rank: Advanced Member

Medals: Bug Buster Level One: Spoon!Level 3: Shirt off your back! Received 25 Thanks!

Joined: 2/19/2015(UTC)
Posts: 254
United States
Location: AZ

Thanks: 8 times
Was thanked: 49 time(s) in 42 post(s)
Originally Posted by: IP Go to Quoted Post
Could the router being preventing the outgoing requests to a DNS and back to itself again?


Yes, either your router does not support NAT Loopback or that feature is turned off. NAT Loopback is required if you want to be able to use the public facing address from computers internally.

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.