I'm stumped

[Andrew Hime]

>Andrew,
>
>Please use Reply To All to ensure that responses go to the mailing list,
>too.

I just hit reply and go, guy.

>"Connection timed out" means that the target computer simply isn't
>responding at all.  It's not a VNC-specific error, but instead indicates a
>more fundamental configuration issue in your network.  Are you sure you
>don't have Windows Firewall, or some other third-party firewall, installed
>on the server computer?

I'm pretty sure I turned Windows Firewall off earlier in the process because I found that it just prevented things from working, even locally from my laptop. There's no third-party firewall software on the box, and as I said - it seems arbitrary as to when it works with no changes. (Seriously, I've barely even started setting up the box for my personal use... I've been a bit lazy lately.)

I understand that connection timed out is not supposed to be a firewalling type issue, and yet that's the setting I was having all the problem with, and the one that tweaking seemed to affect. The box is in the DMZ, so it should be wide open to the Internet. I believe it's got a static IP, but it definitely hasn't changed.

So, it gets stranger... just on a laugh, I fired up my web browser here at work and went to port 5900 on the target box. It loaded the RealVNC java viewer, then... connection timed out.

But how does it know to load that Java app unless the target box responded enough to let it know that's what needed to load? Because this app looked seriously different from what would load before when I would use a browser. So I'm wondering if maybe my old box had an earlier version or something. Anyone got a link to the revision history?

I'm going to check the router one last time when I'm home at lunch, and I guess I'll tweak the port forwarding (on top of the DMZ) if necessary to point to the correct box in excess, but...