access to a web server on a LAN workstation

**mb123** · October 9th, 2005, 10:50 AM

why do you suppose people are unable to access my computer from the internet when they type in my ip address , even though the router firewall is down and i have enabled port forwarding on port 80 to my workstation ip address.

I run a web server on the workstation and would like to make some of the web pages accessible on the internet.

Any ideas are welcome.

thanks

mb123

**NooNoo** · October 9th, 2005, 12:03 PM

Don't take down the router firewall!!! Just make sure the port forwarding is correct.

What server software are you using? Apache? IIS?
What operating system is on the lan workstation?
Is that workstation running a software firewall?

Private message me the IP you are giving your friends to try.

Check that your ISP allows servers - some deliberately block port 80 for outward bound.... in which case move ports.

**mb123** · October 9th, 2005, 12:52 PM

What server software are you using? IIS 5.1
What operating system is on the lan workstation? winXP (desktop)
Is that workstation running a software firewall? no

Private message me the IP you are giving your friends to try.

IP removed to prevent spamming... hence why I asked for a private message.
how do i private message you...?

**NooNoo** · October 9th, 2005, 01:08 PM

OK I assume you can see it on the lan workstation by typing in http://localhost
in the browser?
If not here is a tutorial on setting it up
If you can, then check the second to last page on the above tutorial to check that access is being granted correctly.

On your router - set your logging on and see if people are trying to access it and the router is doing the blocking... or the forwarding. Also check the tutorial for loggin options on your webserver so you can see if it's getting there.

Unable to ping your ip - a tracert shows the ping dies at 203.59.49.73 which is part of the telstra network - implying that telstra is the one that's doing the blocking...

**NooNoo** · October 9th, 2005, 01:16 PM

To private message anyone, either go into the user CP and follow the links or click on the member name on the left of a post - a drop down menu will appear and you can choose to send a private message.

The tracert dies at that address - if your router is the next address, it means pings are being blocked...

**NooNoo** · October 9th, 2005, 01:19 PM

9 9 ms 11 ms 9 ms core2-pos9-2.reading.ukcore.bt.net [194.72.0.253]
10 12 ms 13 ms 12 ms core2-pos5-1.ealing.ukcore.bt.net [194.74.65.229]
11 12 ms 13 ms 13 ms transit2-pos4-0.ealing.ukcore.bt.net [194.72.17.86]
12 11 ms 12 ms 12 ms t2c2-p8-0.uk-eal.eu.bt.net [166.49.168.33]
13 87 ms 87 ms 86 ms t2c2-p4-1.us-ash.eu.bt.net [166.49.164.22]
14 88 ms 88 ms 88 ms gi0-2.ash-core01.net.reach.com [206.223.115.11]
15 87 ms 88 ms 88 ms unknown.net.reach.com [202.40.148.165]
16 114 ms 113 ms 113 ms i-12-0.mia-core01.net.reach.com [202.84.143.78]
17 147 ms 161 ms 135 ms i-12-0.dal-core01.net.reach.com [202.84.143.73]
18 167 ms 167 ms 169 ms i-2-0.wil-core02.net.reach.com [202.84.143.65]
19 316 ms 316 ms 315 ms i-1-3.syd-core01.net.reach.com [202.84.249.206]
20 316 ms 315 ms 316 ms 10GigabitEthernet5-0.pad-core4.Sydney.telstra.net [203.50.13.37]
21 316 ms 316 ms 315 ms 10GigabitEthernet3-0.ken-core4.Sydney.telstra.net [203.50.6.85]
22 329 ms 328 ms 329 ms Pos15-0.win-core1.Melbourne.telstra.net [203.50.6.18]
23 328 ms 329 ms 329 ms 10GigabitEthernet9-0.lon-core3.Melbourne.telstra.net [203.50.6.146]
24 340 ms 340 ms 339 ms Pos1-0.fli-core1.Adelaide.telstra.net [203.50.6.178]
25 369 ms 369 ms 369 ms Pos-channel1.pie-core1.Perth.telstra.net [203.50.6.182]
26 372 ms 369 ms 369 ms GigabitEthernet5-1.pie2.Perth.telstra.net [203.50.115.203]
27 370 ms 371 ms 371 ms chime8.lnk.telstra.net [139.130.25.42]
28 369 ms 370 ms 382 ms gi0-1-17.per-wlte-bras1.chime.net.au [203.59.49.73]
29 * * * Request timed out.
30 * * * Request timed out.

**mb123** · October 9th, 2005, 01:33 PM

ok try now on address 203.59.101.14

**NooNoo** · October 9th, 2005, 01:47 PM

9 10 ms 9 ms 10 ms core2-pos9-2.reading.ukcore.bt.net [194.72.0.253]
10 12 ms 12 ms 12 ms core2-pos5-1.ealing.ukcore.bt.net [194.74.65.229]
11 12 ms 13 ms 14 ms transit2-pos4-0.ealing.ukcore.bt.net [194.72.17.86]
12 12 ms 12 ms 14 ms t2c2-p3-0.uk-eal.eu.bt.net [166.49.168.41]
13 87 ms 88 ms 88 ms t2c2-p4-0.us-ash.eu.bt.net [166.49.164.62]
14 89 ms 88 ms 86 ms gi0-2.ash-core01.net.reach.com [206.223.115.11]
15 88 ms 88 ms 87 ms unknown.net.reach.com [202.40.148.165]
16 114 ms 114 ms 114 ms i-12-0.mia-core01.net.reach.com [202.84.143.78]
17 136 ms 134 ms 135 ms i-12-0.dal-core01.net.reach.com [202.84.143.73]
18 165 ms 165 ms 166 ms i-5-0.wil-core01.net.reach.com [202.84.249.105]
19 315 ms 314 ms 315 ms i-10-1-0.sesstcar01.net.reach.com [202.84.143.210]
20 315 ms 317 ms 316 ms 10GigabitEthernet5-0.pad-core4.Sydney.telstra.net [203.50.13.37]
21 316 ms 314 ms 315 ms 10GigabitEthernet3-0.ken-core4.Sydney.telstra.net [203.50.6.85]
22 328 ms 327 ms 328 ms Pos15-0.win-core1.Melbourne.telstra.net [203.50.6.18]
23 327 ms 326 ms 328 ms 10GigabitEthernet9-0.lon-core3.Melbourne.telstra.net [203.50.6.146]
24 339 ms 339 ms 340 ms Pos1-0.fli-core1.Adelaide.telstra.net [203.50.6.178]
25 369 ms 369 ms 366 ms Pos-channel1.pie-core1.Perth.telstra.net [203.50.6.182]
26 371 ms 370 ms 368 ms GigabitEthernet5-1.pie2.Perth.telstra.net [203.50.115.203]
27 368 ms 370 ms 369 ms chime8.lnk.telstra.net [139.130.25.42]
28 * * * Request timed out.