IIS, hughesnet, and router probs

I've converted my computer to dualboot to XP pro SP1. (yes i know, i know, i can already hear ya'll screaming) and neither IIS nor remote desktop is exactly working.

192.168.1.2 works fine going between computers on my LAN for remote desktop.

192.168.1.2 does work for IIS web pages across network

**.142.***.15 does NOT work for remote desktop

**.142.***.15 does NOT work for IIS webpages.

Internet connection firewall is turned off, there is no windows firewall that i can locate, i added IUSR_admin as a user, I unchecked "automatically detect settings", I've tried with and without network cable connected.

Ports 3389 and my user selected port are both forwarded to 192.168.1.2 at the router.

What have I missed?

Internet IP Address: Get Dynamically From ISP
Domain Name Server (DNS) Address : Get Automatically From ISP
Router MAC Address: Use Default Address

Please select the service type: Port Forwarding
# Service Name Start Port End Port Server IP Address
1 remoteDT2 80 80 192.168.1.2
2 remoteDT3 3389 3389 192.168.1.2

WAN Setup-
Connect Automatically, as Required: checked
Disable SPI Firewall: unchecked
Default DMZ Server: unchecked
Respond to Ping on Internet Port: unchecked
MTU Size (in bytes): 1500

Use Router as DHCP Server: checked
Use a Dynamic DNS Service: off
Static Routes: none
Turn UPnP On: checked

router is a netgear WGT624v3

are there any utilities i can use to find what in the system is blocking it? It passes the telnet test with the 192.168.1.2 IP.

I have this computer set to have a static internal IP.

everything is working fine behind the router.

I completely uninstalled and reinstalled IIS and that at least got everythign working behind the router, but nothing works outside it.

I'm on hughesnet, is there a know issue with it? All the computers are returning the same external IP address even though they have different internal IP's and MAC addresses.

I've done everythign listed on this page: www.testmy .net/t-16654

and yes i've had people outside my network (as in halfway across the country) try to access my external IP and it hasn't worked.

The only question I can think of that would be remotely IIS related is "is IIS running"?

As a comment, update to SP2 if you want to have your web server exposed to the outside world.

it's working on the LAN side of the router so i'd like to assume it's running.

What do you mean about SP2? I'm kind of relucant to upgrade because of all the problems that come with it initially and this is my primary computer.

So is there any way i can track the requests to see where they are getting stopped?

I've tried dynamic DNS as magnethead794.gotdns.org but i have not tested it yet from outside my house. Hughesnet is set up with dynamic IP addresses.

ok i just checked the DDNS using webunlocker.com, still no worky.

Couldn't connect to 67.142.130.29:80: No route to host

Couldn't connect to 67.142.130.29:3389: Connection timed out

Couldn't connect to magnethead794.gotdns.org:80: Connection timed out


If i set up the default DDNS in my netgear router, it works fine as far as going to my hughesnet modem control page but thats the only place i've got it to go on my network that worked.

I also went to my network connections, internet connection,and set ports 3389 and 80 top open. Still no worky.

since IIS is running on the LAN side, this is not an IIS problem, moved from the IIS folder.

Perhaps your ISP is blocking port 80.

ack! took me a few minute to figure out why this wasn't listed in the IIS forum and where it was.

So do i just go back to IIS management and change port 80 to some other random port?

I just talked to hughesnet CS, they say that they do not block any ports at all and i checked the firewall in the modem and it is disabled.

Couldn't connect to 67.142.130.29:80: Connection timed out

Couldn't connect to 67.142.130.29:2007: Connection timed out

Couldn't connect to 67.142.130.29:3389: Connection timed out

Couldn't connect to 67.142.130.29:80: Connection timed out

Well, if as you say your web page opens up from the internal LAN, then you definitely have something blocking http traffic somewhere in your network.

Yes, you could try some alternate port in IIS like port 8080 and see what happens, but if as I suspect you have a firewall that's not opened, then the alternate port probably won't work either.

Here are some more configuration settings, they're for the LAN connection on windows.

IP settings:

DHCP enabled

DNS:

DNS servers: empty
append primary and connection specific DNS: marked
append parent suffixes of the primary DNS suffix (checked)

register this connections addresses in DNS (checked)

WINS

enable LMHOSTS lookup (marked)

NetBIOS: default

options

TCP IP filtering

enable TCP/IP filtering (all modes) unchecked

TCP: permit all
UDP: permit all
IP: permit all

also, on internet connection services, i have remote desktop port 3389 set to allow on UDP (just changed to TCP).

I'll try directly connecting to the modem and see what that does. As far as I can tell the ports are forwarded correctly at the router, internet connection firewall is turned off, and hughesnet has an open system at their servers and the modem.

edit- something i've failed to mention: there is also a Hewlett-packard procurve 408 SWITCH in the line between my computer and the netgear broadband router.

edit2: bypass switch, no difference

Have you forwarded port 80 through your router? And why did you mention ICS, which isn't something you'd normally enable when you have an external router.

actually, i have no clue why ICS is on. for some reason on XP pro it wont recognize that i'm connected to the network and getting internet through that network on the connection wizard. I have to select residential gateway or i dont get internet at all. On xp home it doesnt even list me as having a high speed connection, it just lists the LAN connection.

on a similar note, all my computers i have on pro are set up that way.

might that be interfering?

this is on the UPnP page on ym router.

Active Protocol Int. Port Ext. Port IP Address
YES UDP 25002 25002 192.168.1.2
YES TCP 80 80 192.168.1.2
YES TCP 3389 3389 192.168.1.2

and port forwarding..

# Service Name Start Port End Port Server IP Address
1 HTTP 80 80 192.168.1.2
2 remote_1 2007 2007 192.168.1.2


and for who knows what reason port 3389 disappeared from the port forwarding page. It says port conflict with another service.

ok i'm straight onto the modem now and it's still not working. I think it's safe to say it's something with hughesnet. Either that or there's something on my computer.

is there any kind of program i can doanload that will trace everything until finds what's causing the problems?

Couldn't connect to 67.142.130.11:3389: Connection timed out

Couldn't connect to 67.142.130.11:2007: Connection timed out

Couldn't connect to 67.142.130.11:80: Connection timed out

edit- i found http://www.canyouseeme.org/ and i'm checking ports 3389, 2007 (user spcified on IIS), and 80. none of the 3 are passing.

I had a problem similars as yours time ago with my DSL router. They told me the same stuff, "All ports are open, we have no restriction on the router". After I got access to my router, I look in to the web configuration page and found nothing there, everything look fine. So I move to the telnet session. When look in to the NAT parameter I found a LOOP back to the IP 127.0.0.1, So any request coming from internet will receive a look back from the same router. I remove the look back and everything is working since then.

Hope this could work for you.

I doubt if after one year this problem still exists.. please don't
resurrect old threads - thanks for the advice, it might be
useful for other people with the same problem.

--thread closed.