Internet > Static Public Ip on Dlink Router 192.168.1.1 > < 192.168.1.2 SBS2K Server 192.168.0.1-254 > Workstations and Linux Web server on IP:port 192.168.0.222:10000
I can access the the internet from all internal workstations and have exchange running just fine on the sbs server I can access the linux server internally by using 192.168.0.222:10000 and it works a treat but I have tried just about everything to get access it from the internet with no success. I would like to access it by typing public ip & port ie 188.8.131.52:10000 Port 10000 on the dlink router is forwarded to 192.168.1.2 the sbs box.
Could anybody please help with some instructions on how to configure ISA I am a relative newbie.
Just to make sure, does your ISP allow incoming connections on this port? Do you know of any port restrictions your ISP has? You have SMTP working (you published Exchange) so I doubt they're blocking 10000, but I just thought I'd add it.
1. In the ISA admin console, go into Firewall Policy and select the Tasks tab on the right 2. Select the option to 'Publish a Web Server' 3. Provide a name for the rule 4. Select Allow 5. In the Define Website to publish dialog, enter the following information...
Computer Name: 192.168.0.222 Forward the original host header - Disabled <not required> Path: /*
6. In the Public Name Details dialog, enter the following information...
Accept Requests for: Thei domain name (type below) Public Name: 184.108.40.206 Path: Leave it set to /*
7. In the Web Listener dialog, select New and enter the following information...
Name: Web Listener <10000> IP Addresses: External Port Specification: Enable HTTP enabled | HTTP Port: 10000
8. Hit next once the Listener is selected 9. User Sets: All Users for now 10. Hit finish
This is all you need to get access to the URL. If this doesn't work, go step by step and see where it's failing
Can you telnet to ISAs External IP on TCP 10000 (in Windows, 'telnet 192.168.1.2 10000' at a command prompt) If yes, then what does ISA report under Monitoring\Logging during the connection attempt - you might add an entry for "Client IP Equals YourTestClientIP" to help limit the results.
< Message edited by ClintD -- 17.Feb.2006 7:36:08 AM >