Lorenzo:
Heya. Some suggestions for you to try:
> Problem 1:
> Can't even telnet from the laptops to the server using
> telnet 192.168.1.3 5900. Can't use VNC viewers to
> connect to it either altough the server registers just
> fine.
So on your Win98 server, when you put the mouse over
the VNC icon in the lower-right service tray, what IP address
comes up? And just to be sure you're connected, what happens when
you "ping 192.168.1.3" from one of your other LAN machines?
If you cannot VNC from a laptop inside of your LAN to
your VNC server, my initial reaction is that either your VNC
service isn't really running, or it has a AuthHost value set
in the registry which prevents your other LAN members from
connecting. Type "Start -> Run -> regedit" and look for a key
in "HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\" called AuthHosts.
If it's there, delete it.
Once you can connect from inside of your network, you
can then try connecting from outside of your network. The script
at "www.GoToMyVNC.com" will test the connection for you and let
you know if your firewall/router is port-forwarding everything
correctly.
> Problem 2:
> When I connect to the url provided by my no-ip.com
> service, name.myvnc.com or my WAN IP, I get a login
> prompt for my router's admin settings....
Yes, your router is listening to port-80, which is what
your browser connects to by default. You'll need to tell your
browser to connect to port 5800 where VNC's builtin http service
is listening: "name.myvnc.com:5800", for example.
Good luck!
-Scott
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
