Must be more to it than that. I am running several other servers on the
same machine (Apache, FTP, Fictional Daemon, etc) and I have no problem
accessing them from the outside. In netstat, they show up bound
specifically to both "inside" and the "outside" IP addresses, not 0.0.0.0.
e.g.
12.34.56.78:80 LISTENING (ok)
12.34.56.78:23 LISTENING (ok)
0.0.0.0:5800 LISTENING (fails)
0.0.0.0:5900 LISTENING (fails)
HH
----- Original Message -----
From: "James ''Wez'' Weatherall" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 08, 2001 11:14 AM
Subject: Re: VNC Server on multihomed host
> > Hello. Excuse me if this question has already been asked. I couldn't
> find it
> > in the FAQ.
> >
> > I have a multihomed Win98SE host. When running WinVNC server,
> "netstat -a -n"
> > shows winsock listening on "local network" ip address "0.0.0.0:5800" and
> > "0.0.0.0:5900" rather than the "outside" ip address. Consequently, I
cant
> > connect to the server from outside.
>
>
> This is not the cause of your problem. Listening on 0.0.0.0:xxxx means
> "listen on any incoming network interface, on the specified port".
>
> Cheers,
>
> James "Wez" Weatherall
> --
> "The path to enlightenment is /usr/bin/enlightenment"
> Laboratory for Communications Engineering, Cambridge - Tel : 766513
> AT&T Labs Cambridge, UK - Tel : 343000
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
