Windows 2000 Server problems, won't broadcast beyond my router

Ok So I want to start a webserver. My new room mate had a Windows 2000 Server box and so we set up IIS on the server. When I connect to the the assigned ip in the network, 192.168.1.102 I get my webpage, but when I'm outside of the network and I enter in my ip, 69.134.148.31. I get nothing. I got this ip from www.whatismyip.com Futhermore I plugged my internet directly into my windows box and it still didn't get anything (my ISP does not block any ports I know this for a fact). Futhermore, whats weirder is my ip without the router from whatismyip.com is 65.190.138.127, but when I plug it back in it is 69.134.148.31. I have posted on so many other forums and no one has any ideas. I understand it's easier to fix something when you're there so I am more than happy to post screen shots of anything you want to see as long as you can try to help me. Here are a links to screen shots of my set up

http://i220.photobucket.com/albums/dd160/jrb599/1.png
http://i220.photobucket.com/albums/dd160/jrb599/2.png
http://i220.photobucket.com/albums/dd160/jrb599/3.png
http://i220.photobucket.com/albums/dd160/jrb599/4.png
http://i220.photobucket.com/albums/dd160/jrb599/5.png

 

anyone?

 

You need to enable port forwarding on your router. You need to port forward port 80 to the internal IP address of the server 192.168.1.102.

What is the make and model of the router?

 

WRT300N V1.1 Linksys Wireless N

 

Port Fowarding is on, if you look at the pics I posted you should be able to see it was done.

 

Is the 2000 server running ISA?

 

What is ISA?

 

Well it's not the router because I just got through using RDP.

 

How did you get through? The computer is off.

 

Oh Nevermind.
I forgot this new version of RDP asks for credentuals before it ever connects.

 

I think wireless N router and Windows 2000 may not be compatible.

 

Doubt it. That has nothing to do with it.

Can you do a tracert to www.yahoo.com and post the result?

 

I see the problem. Your on a MAC.

 

How do I tracert

 

I'm a little suspicious of that second hop. There may be some port 80 blocking going on.

Try changing your page to port 8080 and come in from the outside using http://yourip:8080

Don't forget to forward 8080 in your router.

 

I think that second hop is very significant. You've got two networks!!!!! a 10.0.0.0 network and a 192.168.0.0 network. That means two routers and potentially, a much more complicated connection to the internet.

What is the internal address of your internet router?

How is your computer connected to the server - what devices sit between you and the server?

Does the server use the same router as you to connect to the internet?

 

Looks like his ISP is redirecting http:// through a proxi.

 

Actually, looking at the original post the 10.0.0.0 network may well belong to the ISP or network provider.

I think it is more than just a HTTP proxy. Tracert uses ICMP so wouldn't be affected by a simple HTTP proxy

 

I've looked at it again - gone through all the screen shots.

The problem is that Jrb599's network is inside a second private network. That means there is a second NAT between the web server and the internet. To get the webserver accessible from the internet, you also need to set up port forwarding on the 10.126.0.1 router.

I notice the server belongs to a "new room mate ". Are we talking university/college residence? If so the problem is that Jrb599 is connecting to the internet via the university/college network. The only way you are going to get server access is if the administrators of the 10.0.0.0 network allow it and set it up!!!!