The Natural Philosopher wrote:

> monskie wrote:
>> Hello guys,
>>
>> Please excuse my post. I'd like to ask for some assistance or
>> your expert advice on how to go about my problem. This
>> concerns having Linux as my internet gateway and a Windows
>> 2000 server as a web server.
>>
>> I still consider myself a newbie to linux. I have
>> a small office network and here are my server setups
>> in particular to what I have mentioned.
>>
>> 1.) Linux Server (acting as internet gateway)
>> + Redhat v9.0 (Shrike)
>> - Firewall-Jay v0.91
>> (IP: 192.168.1.254)
>> + Connected to a DSL
>>
>> 2.) Windows 2000 Server (Acting as web server)
>> + IIS 5.0
>> + .NET Framework
>> + .NET web apps
>> (IP: 192.168.1.9)
>>
>>
>> Goal:
>> - Users should be able to access my web apps in my webserver
>> from the internet via port redirection/forwarding to port 82.
>>
>> Current Scenario:
>> 1.) The Window Server (webserver) is currently connected
>> to a Windows Domain (AD), and the linux server is not connected
>> though they reside on the same network/subnet.
>>
>> 2.) I have already configured the linux server as an internet
>> gateway for my small network and is already working.
>> I have also set the Firewall-Jay for some port blocking.
>>
>> 3.) I have also configured Firewall-jay (linux server)
>> for port redirection on 82 to port 80 of the webserver
>>
>>
>> Problem:
>> 1.) I've tried accessing the webapp from inet using
>> the public IP with port redirect to 82 but it seems
>> it cannot reach or find the application
>>
>>
>> I've tried looking for some info on linux and windows configuration.
>> The internet has enourmous information on this matter and I had
>> a hardtime looking for that particular info that will address this
>> problem.
>>
>> Guys, can you suggest on how should I go about this problem. I would
>> much appreciate if you can provide me a guide list on addressing this
>> problem. from there, I can look further from inet for instructions
>> and procedures in configuring linux and windows. I would also
>> appreciate
>> URL's providing references, or perhaps ebooks touching this
>> kind of scenario or problem.
>>
>> Thank you very much,
>>
>> mon
>>
>
> Possibly because web servers live on port 80?
Yes, i think that the mapping is backwards also. If the abnormal port is
what is intended (pretty much blocking out public access) OP should use a
port directing form of url, ala "http:82//www.whatever.domain".
--
JosephKK
Gegen dummheit kampfen Die Gotter Selbst, vergebens.
--Shiller