大网数据广告活动
网站运营与故障问答

Can't access website from same network

· 52CE 我爱测

I've setup IIS locally to host a website. I've created a free NOIP account so I can access it with a domain name. It's temporary, so I plan to assign a real domain to it later. I setup port forwarding on the router. Everything is…

问题原文

原帖链接 · Charlie74 · CC BY-SA 3.0

I've setup IIS locally to host a website. I've created a free NOIP account so I can access it with a domain name. It's temporary, so I plan to assign a real domain to it later. I setup port forwarding on the router. Everything is in place.

I spent hours yesterday trying to figure out why I can't access the website via my external IP / hostname. I can access it locally from the same machine using localhost. I can access it locally using another machine by using the IP address. But I can't use the hostname or external IP address. I believe it must be a router setting.

Today I attempted to access the site from another network, and it works just fine using both the public IP address as well as the hostname. However, from my home network, where I'm running this, I can't use the external IP to access the site; only the internal IP.

My question / concern

Based on all of the above I'm concerned that my provider (Comcast) might be blocking access in some way, though I wouldn't have a clue as to where to start to check. Is there any reason I shouldn't be able to use an external URL to access my site? It seems I should be able to use both the internal and external IP and get the same results.

Thoughts? Suggestions?

Update

To attempt to rule out a server config / Windows issue, I wiped the box, installed Ubuntu on it, and just completed a LAMP installation. Unfortunately, it has the same issue. From within my home network I can access the web page with my internal IP address, but not the external IP or hostname. On another machine, outside my home network, I can access the webpage using the external IP and hostname.

I'm curious if others can access it also. If you don't mind trying and posting in the comments below, the temporary URL is http://cfsamet.noip.me. I'd be curious if anyone other than myself is having trouble accessing the site. It's the default Apache for Ubuntu page right now.

Update #2

No luck yet. Have tried to connect internally using my MacBook, Windows, Linux, even my iPhone. All fail when using the external IP or URL, but can connect fine if I use the internal IP address. I can only assume it's a router issue, or a Comcast issue... not sure I'll get much further here. I'm mostly just stumped at this point.

I've tested using http://www.gomeznetworks.com, all of their servers can access the site just fine. I've also tested using http://tools.pingdom.com. It can access the site as well. It seems that I'm the only one (from home) that can't access my site. How does that even make sense?? LOL.

Solution

Unfortunately, this was put on hold... but I did essentially find the answer to the problem. This is a hardware issue with the Comcast modem used. This link - http://forums.comcast.com/t5/Home-Networking-Router-WiFi/SMCD3G-Can-t-access-web-server-from-LAN-from-Internet-OK/m-p/1754823#M55009 - has detailed information that explains the router is re-routing requests back internally without doing a DNS lookup. This is why things fail.

已采纳解答

原帖链接 · Charlie74 · CC BY-SA 3.0

After much research, I found this article on the Comcast forums: http://forums.comcast.com/t5/Home-Networking-Router-WiFi/SMCD3G-Can-t-access-web-server-from-LAN-from-Internet-OK/m-p/1754823#M55009

Essentially, certain models of Comcast routers (both home and business class) will experience an "issue" where requests made from inside the network "die" at the router. It has to do with NAT, and it appears that some routers will send the request up to the DNS server to resolve, and some will stop the request right there.

The "solution" is to just use the internal IP address of website... though I am disappointed by this, as it seems silly to me that the router can't resolve itself. But, it is what it is.

Hopefully this answer helps anyone else running in to the same issue as myself... trying to figure out why a site can be accessed externally and not internally.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2014-05-13)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。