This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
My home server url wont connect when connecting on home network
I have recently moved from an ASUS AC66U to a Nighthawk X4S.
I have a server on my network with the url https://myserver.com for example. If I try to connect from home with the url it wont connect but if Im at work it will.
I have all the required port forwarding set up.
With my ASUS I was able to enter a command into the router via the admin settings page that would loop back a url request for an address on the local network to the router from the internet. Then I could use my url while on the same local network as the server.
Re: My home server url wont connect when connecting on home network
> I have a server on my network with the url https://myserver.com for > example. [...]
So, you're talking about a web server? Listening at port 443?
> [...] If I try to connect from home with the url it wont connect but > if Im at work it will.
Is your "my network" your "from home" network or your "at work" network? You're using exactly the same URL in both places?
> [...] I have all the required port forwarding set up.
Perhaps. It would build confidence if you showed the actual address reservation(s) and/or port-forwarding rules, rather than telling us how perfect they all are. Copy+paste is your friend.
> With my ASUS I was able to enter a command into the router via the > admin settings page that would loop back a url request for an address on > the local network to the router from the internet.
"NAT loopback" should work with a Netgear router, too, but Netgear router firmware is not always bug-free.
> Can I get this set up with my new R7800 X4S?
Firmware version?
Can you access this server from a system on the server's LAN using the server's LAN IP address? Using the router's WAN IP address? From off-LAN using the router's WAN IP address? What are all these IP addresses? (The first two octets of what should be your public IP address ("a.b" out of "a.b.c.d") will do, if you don't want to reveal the whole thing.) Is the problem with the port forwarding, or with the DNS name resolution of "myserver.com"?
