Re: [coLinux-users] Steps to redirect ports in SLIRP mode ?

[Henry N. <Hen...@Ar...>]

Frédéric L. W. Meunier schrieb:
> On Jan 23, 2008 6:53 PM, Henry Nestler <Hen...@ar...> wrote:
>> Frédéric L. W. Meunier wrote:
>>> On Wed, 23 Jan 2008, Henry Nestler wrote:
>>>
>>> Everything you both listed is right, but http://localhost/
>>> doesn't work from Windows. It does only if I run a native
>>> Windows server.
>> I don't know your difference you means.
>> Windows != Windows Server ?
>> If not native Windows? What else is it?
>>
> 
> I meant Windows = XP Professional and Windows server = a Windows HTTP server.
> 
>>> In TCPView, I see:
>>>
>>> colinux-slirp-net-daemon.exe TCP PERVALIDUS:80 PERVALIDUS:0
>>> LISTENING
>> Please disable DNS Name Resolution on TCPview. It should be listen on
>> 0.0.0.0 (every networks)
>>
> 
> It returns 0.0.0.0.
> 
>> Try other port for remapping, for example
>>   tcp:2222:22/tcp:4000:80
>> Than on the windows side the port 4000 is your webserver and port 80
>> inside coLinux. Type the URL http://localhost:4000/ in your Windows browser.
> 
> Remapping, both work.Now I really don't have any idea why using the
> same ports doesn't.

Only one program can agent as server on one tcp port.
If you have a running program that is listen on port 80 (windows web
Server ?), than an other program can not open the same port for listen.
Or ir can open, but windows is faster and catch all the incommings. I
don't know.

Has your windows some more protections to not open ports lower than 1024
from a user program as server? Some firewalls or secure tools forbidden
and and blocks it (Zone Alarm, Norton, ...).

For example on Linux an user land program can only listen on ports
>1023. On ports 22 and 80 only a user "root" can listen.

-- 
Henry N.