• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Having problems reaching web server on VMware..

aceO07

Diamond Member
I'm having trouble reaching my webserver running in VMware.

Computer hosting VMware is 192.168.1.100
VMware session with webserver is bridged and set to 192.168.1.200
Router is set to forward port 80 to 192.168.1.200.

I can access the webserver through it's assigned domain when I'm on the lan. webserver.com. However, I can't access it from outside. When I ping webserver.com from outside, it will go to the right IP address that is assigned to me. However, it times out when I visit the webserver.

Any suggestions of things to check?
 
The port may be blocked by your ISP. Try running a remote port scan on your IP and see if it detects any open ports.

Jim
 
Thanks. I'll look into that.

A quick google search brought back results that Verizon DSL does seem to block port 80 for some people. I'll check it out once I get home. I might try 8080 too.
 
you might be double natted as well...there are lots of DSL modems that are modem/router combos. You might also update the f/w on your router
 
I just checked. Port 80 is closed. Port 8080 is open, so I'll use that. Too bad browsers don't fall back to port 8080 if port 80 isn't available.
 
Originally posted by: aceO07
I just checked. Port 80 is closed. Port 8080 is open, so I'll use that. Too bad browsers don't fall back to port 8080 if port 80 isn't available.
Then Verizon would block 8080, too. 😉
 
hmm.. I thought 8080 was another standard port for web servers? Apache uses 8080.

What would you recommend as another port to use?
 
hmm.. I thought 8080 was another standard port for web servers? Apache uses 8080.

My services file says "webcache 8080/tcp # WWW caching service". But it really doesn't matter except for what clients default to and you already know that won't work for you, as long as you don't have anything running to conflict with the port it's selection can be completely arbitrary.
 
Back
Top