• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 480
  • Last Modified:

Router setup problems (cannot connect to domain)

Hi Experts,
The background and environment:
1. WIndows Server 2008
2. ASUS RT-N13U router
3. Public IP incoming via PPPoe
4. FileZilla as FTP server
5. Web-Server on HyperV on Main server 2008

All is working fine. Internet connection working fine. I can access any site from all workstations and server.
Web server is functioning fine from within the LAN.
domain name resolves correctly to public ip when ping from inside the LAN and site opens fine from the LAN.
Problem is from the WAN. I cannot ping the domain nor public ip from the internet (WAN)
I assume this is a routing problem but cannot find the problem.
please help
2 Solutions
I assume that you are using NAT on the router, so the internal machines are on an unconnected network 192.168.x.x or 10.x.x.x etc ??

If so, you then need to configure an inbound rule for the web server ports, normally port 80 pr 443 if its a secure site, to basically route any inbound connection to the internal server address.

Your router is prolly set to discard icmp requests. Wayne is correct, you will need to setup port fowarding. One probelm thought, alot of time ISP's will not allow you to run a webserver from home, ie block port 80 inbound. I would suggest setting up port fowarding first. You will need to foward port 80 to your webserver and port 21 to your ftp box. To test if you have this configure correctly you can run a scan for open ports via the web. Go to this website to check once you forwarded the ports, http://www.grc.com/default.htm  go to sheilds up/
espsAuthor Commented:
Excellent correct and clear advise.
Great site you referred.

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now