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

[<lis...@pe...>]

On Jan 23, 2008 6:53 PM, Henry Nestler <Hen...@ar...> wrote:
>
> Fr=E9d=E9ric 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 !=3D Windows Server ?
> If not native Windows? What else is it?
>

I meant Windows =3D XP Professional and Windows server =3D a Windows HTTP s=
erver.

> > 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 brows=
er.

Remapping, both work.Now I really don't have any idea why using the
same ports doesn't.

> > I don't have any firewall running on Windows, but added
> > colinux-slirp-net-daemon.exe to the list of exceptions in
> > Windows Firewall.
>
> If you have no firewall on windows, why you can add exceptions to
> firewall? Try complete disable the windoes internal firewall. If you not
> would risk some, you can disconnect your networkcable for this testing
> time. Slirp is usable from windows to coLinux and via versa without any
> external network.

Windows Firewall is "off", but even with it disabled, the "Exceptions"
tab is enabled. Just for safety, I had added
colinux-slirp-net-daemon.exe to the list.

> Check: We talk about coLinux 0.7.1, 0.7.2 or 0.8.x? Not older, please.

0.8.0-20071105.