Win 2003 Server Security Preventing Browser (IE) Based Access outside of Network?

I am configuring web server / app. server for remote access via IE browser. Temporarily have said server sitting on local peer to peer network behind router that is connected to cable modem. No firewall on server, just router firewall. I am able to access the server and the application from a local workstation on the network by keying in www.domainname.com. Haven't been able to access the server from outside the network at all.

Router has port 80 enabled. We haven't had any problems with network workstations having full Internet access.

On the IIS Web Services Extensions, I've allowed Active Server pages, ASP.NET, Internet Data Connector, and Server Side Includes. Any suggestions?

TIA, Dan
odanthemanAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Computer101Connect With a Mentor Commented:
PAQed with points refunded (250)

Computer101
EE Admin
0
 
AnthonyP9618Commented:
Are you hitting the web server at all from outside the network? Any info from the IIS Logs, Windows Security event logs?
0
 
inbarasanCommented:
Is the external DNS resolving this Domain Name on the system with which you are testing. Kindly check it. If yes then To check if the port is open do the telnet test.

Here is the syntax below

telnet www.domainname.com:80

It should open the windows in listening mode. If the port is closes then it will give port is closed error

Check it and post the info so that we can debug some more.
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
odanthemanAuthor Commented:
Good Morning!

Anthony, I've looked at the Security and System logs under Event Viewer. Don't know exactly what to look for. Nothing jumps out. Haven't set up specific IIS log.

inbarasan, did telnet www.domainname.com 80 from command line and connected (gives me blank screen).

I'm able to ping the domainname both locally and globally and get back the IP address.

0
 
odanthemanAuthor Commented:
Don't know what happened to break off communication with AnthonyP9618 and inbarasan.

In meantime, been trouble shooting and realized ISP (RCN Cable) blocks port 80. I can reroute to port 8080 in Win 2003 Server and DNS2GO, but my D-Link router is hard wired to port 80. So I'm checking out  LinkSys routers that will allow port changing.

Cheers,
Dan
0
 
odanthemanAuthor Commented:
Conclusion: Found solution to my problem by reconfiguring my D-Link DI-624 router. Changed the Admin port from 8080 to another port and was then able to change primary port from 80 to 8080. Remote browser access on port 8080 now works fine.

Dan
0
All Courses

From novice to tech pro — start learning today.