Andy Bruce - softwareAB
andy "at" softwareab.net
Fri Jul 22 21:31:00 2005
192.168.0.x is generally a wireless network (most home PC routers use
192.168.1.x for a wired network). My guess is that you are bound to a
different network card than you think.
Also, since generally PC routers assign IP addresses starting with
"192.168.x.50" then it appears that your 192.168.0.2 is a static IP
address. This might be on purpose; certainly when NAT'ing external
requests thru your router it's easiest if the destination PC on your
local network has a static IP address.
1. Open DOS command prompt (Start/Run, "cmd").
2. Type "ipconfig". That will show you the network interfaces active.
3. Type "ipconfig /release". If you are using DHCP, that frees the IP
connection. If you aren't using DHCP, the command gives a cryptic and
scary (but harmless) error message which you may ignore.
4. Type "ipconfig /renew". Same notes for above.
5. Go to services (Start/Control Panel/Computer Administration/Services)
and restart the VNC Server service.
6. Flyover the VNC server icon on the systray and see if it has bound to
the same IP address.
Also to try after doing the previous:
7. From the DOS prompt, type "netstat -a". Look for the 5900 port. It
should be LISTENING.
8. Try connecting to your local box using telnet ("telnet localhost
5900"). You should end up with an empty screen with something like "RFB
003.008" at the top. If so, you are truly listening on 5900 (which is
all that EchoVNC verified, right, Scott?). Use Ctrl+C and press ENTER a
few times to break the connection.
9. Verify that, on your router, you are truly forwarding port 5900 to
192.168.0.2 (if that is, indeed, the correct IP address).
Other than that, it's got me stumped. I'd say "open your machine and
we'll check it out for you" but that's unfortunately the problem you're
trying to solve :)
Aaron Hill wrote:
>I just downloaded a copy of EchoVNC and it is not detecting my VNC Server
>even though when I fly over it in the systray it shows VNC Server
>(Service):192.168.0.2. There may be something to your idea that the VNC
>Server is bound to a different network. My guess though, being that this is
>a home PC meant for the very average user, there is only one network card.
>I have had other people sniff the ports and found that 5900 is open and
>accepting connections. So, I downloaded Ethereal 0.10.11 and quickly found
>out that it's a program way over this novice's head.
>If I'm Port Forwarding port 5900 properly, If VNC Server is running
>properly, if my ZoneAlarm firewall is properly set to allow such connections
>(or diabled) what could be the issue? Any ideas?
>From: Andy Bruce - softwareAB [mailto:andy "at" softwareab.net]
>Sent: Friday, July 22, 2005 12:35 PM
>To: Aaron Hill
>Cc: vnc-list "at" realvnc.com
>Subject: Re: Cannot connect
>If you've tried everything else, download free trial of Ethereal and
>sniff the port. It will tell you if anything is making it in. It sounds
>to me like "something" is blocking what you've got.
>On a more local note--when you run VNC in service mode you should get
>the VNC icon showing up on your system tray. Try flying over it and see
>if you get a display like "VNC Server (Service): 192.168.1.105" (that's
>my local address, obviously to have it NAT'ed through the router I have
>to enable port forwarding to my local box).
>I've found it's not unusual for someone to flyover their systray item
>and it happily reports that the VNC server isn't really listening. Also,
>the VNC server could possibly be bound to the wrong network connection
>if you have multiple network cards in your box.
>Aaron Hill wrote:
>>New to VNC and new to networking in general but like most everything, I
>>right in. I have VNC Server set up in service mode on my home PC (XP).
>>Every attempt to connect to my server PC from an outside internet
>>has been blocked. I can connect to other PCs with the viewer and I can
>>remotely access my PC with my laptop when it is connected to the LAN. Port
>>5900 is wide open and can be sniffed by gotomyvnc.com. I have read many
>>other posts regarding connectivity issues and tried several of the
>>with no success. I am concerned that there is a software program that is
>>blocking the connection. I have Windows Firewall diabled and even tried
>>completely disabling my ZoneAlarm Firewall with no luck.
>>Could this be the result of a program blocking the connection or VNC Server
>>rejecting the connection?
>>VNC-List mailing list
>>VNC-List "at" realvnc.com
>>To remove yourself from the list visit: