Need Help To Setup Iis

[smartegyptian]

My router assigned 192.168.2.31 as my IP I'm trying setup my IIS (xp pro) when I add my real ip address in the "default website properties screen" under Services and Applications > Internet Information Service> Web Sites > rite click then Properties
nothing seams like it's working I pretty much went thru all the settings

Any Ideas

[twwabw]

Port forward from your router to the client internal IP running IIS. You don't assign it the public IP if you're running through a NAT router.

[smartegyptian]

Do I have to static the connection to the router instead of using DHCP to have IIS to work

[twwabw]

Static lan ip is not a requirement, per se. But, it IS a requirement for port forwarding. You can't port forward to an internal client whose IP changes all the time.

[smartegyptian]

My internal/external IP don't change it seems like I been having a problem to setup IIS because of the router

[cyberskye]

Some routers do require static addressing on the LAN to use port forwarding - especially the ones that don't do reservations.

What error message are you getting when you try and browse the page? That can help determine the point at which things are getting hosed.

Skye

[catngo]

first, make sure you set the router in the section "virtual server" choose port (80, 8080,...) and IP which is the server IP (internal IP 192.168.xxx.xxx). then have the server using same port that you specified in the router. Now, access the website using WAN IP. it should work. if not and if you using port 80 for your server, you may want to check see if it got block my your ISP (most broadband ISP block port 80). if that the case, try using different port (8080, 82, 83, .....).

[cyberskye]

Some routers don't handle loop-back well. If you are behind the router trying to access a webpage also behind the router - all by way of the public ip address...I've had problems with this behind a Linky. Killed myself trying to figure it all out but it was working all the time.

Skye

[smartegyptian]

I have Microsoft Broadband Networking Wired Base Station MN-100 I'm also on DSL www.verizon.com
I don't know how to make it to work...?
*I do have port forwarding
Application-Triggered Port Forwarding and Persistent Port Forwarding (What I need )

http://www.theforumisdown.com/uploadfiles/0103/mjj.jpg
copy and past in your browser to see it

[BOWTYE8]

I am running a basic IIs service with dsl and a linksys router.

My dsl has a dynamic IP(always changes)
I have my linksys port fowarding "port80" of the assigned IP addy from the linksys. I let my linksys act as the dchp server(assigns the local IP addy's...eg. PC1=192.168.1.101, PC2=192.168.1.102) if the server PC is on 192.168.1.102 then foward port 80 with this IP addy in the router config settings.

As for IIs setup on the PC. I have done nothing special. You shouldbe able to load IIs. Once the router settings are set. Typing in your ISP obtained IP addy shoyuld give you the default webpage.
Also check you PC firewall settings. If you are running zonealarm you will have to allow IIS to act as a server.

This may not be you exact setup but just trying to help. I belive most router configurations are very similiar.

One final note. I mentioned my IP always changes. I use the TZO service to foward my changing IP to my domain name.

Dennis

[smartegyptian]

Thx Guys
Can someone look at my image here and try to help me out little more
http://www.theforumisdown.com/uploadfiles/0103/mjj.jpg

[smartegyptian]

Any1

[catngo]

how about zoom it in a bit?

[smartegyptian]

I can't do better than this

www.theforumisdown.com/uploadfiles/0103/dfdf.gif

[catngo]

http://www.atomzone.net/images/mjj.jpg

The last 2 box is for port tuneling. let say you have website running on port 80 and chat server running on port 6667, you can put 6667 in those box (2nd box always for range setting) and have router tunel port 6667 to 80 then you dont' have to open port 6667 on router.

* make sure your server using static ip and your ISP give you static IP. you would hate to track down your IP and call your friends everyday and say: " Hey, this is my new website http:///xxx.xxx.xxx.xxx"

*check make sure the port your webserver running doesn't block by ISP (you can call them and ask but it so obvious or you can check with PORT SCANNING SITE)