Win 7 pro/OpenVPN/TightVNC remote access problem over vpn

I have a small WS 2012 R2 domain at work with 8 Win 7 pro workstations.

At home I use openvpn & tightvnc to connect to the domain from a win 7 pro box and log onto any machine. VPN and TightVNC work perfectly

Just put in another win7pro box at work. Domain controller sees it, other workstations see it and I can connect to it on the local lan from any other box with tightvnc. Can ping to and from.

At hone I cannot ping or connect using TightVNC or remote desktop. Can only access the box by logging into another box with TightVNC then instigating a session to the new box. This works, but the latency is a obviously a problem, and doesn't solve the primary requirement of a direct connection.

Can't just pop into work, its a 25 mile round trip, so really need some pointers as to where I need to look for issues. I am thinking its windows firewall, but can't see anything different from the other boxes.

Bit slow and difficult to view the logs remotely, I'm at the workplace tomorrow so will grab the logs to investigate. In the quick look just now via the server machine and a local TVNC session, in the Application logs it recorded the tightvnc access when I logged in, as Authentication passed by the server ip, event 247, tvnserver. I tried to initiate a remote connection which failed of course and there was no entry in the destination machine Application log so I guess it didn't get that far. There are a lot of entries HHCTRL with ID 1904.

This is not an area I have much expertise in so which logs would be relevant to examine? And is there a quick way to dump them onto a portable drive to examine at home?

However, the fact that you can't tracert or ping to the computer in question means you probably do have some type of firewall issue that's blocking access from the outside. Do you have any type of hardware firewall at work? Are there any firewall rules or groups that the new computer has not been assigned?

I am in at work tomorrow (Wed) so will have a good look at the machine in question, too difficult over the tunnel. We use Norton AV on all the workstations so I will check that setup as well.

Strange that I can tracert and ping the box when on the local lan, and also access it with TightVNC and Remote Desktop, but only get to the machine over the vpn by logging into another lan box then invoking a TightVNC session from that box). Has to be something in the machine setup rather than a network issue?

Well I had a good look at the problem machine, it is visible on the domain and has similar network settings to other machines which I can access over the vpn. Access to it via TVNC works perfectly whilst on the domain lan, either in person or by logging into another box over the vpn and initiating TVNC from that box.
Could see nothing in the logs relating to login attempts but I don't really know what logs I should be examining. The machine has a fixed ip, as do the other machines I can access.
Tracert to another machine (but not the openvpn server) returns the first hop to the virtual ip of the openvpn server and the second hop to the machine in question. Doing the same to the problem box, shows the first hop to the virtual ip then the remaining hops time out.
Don't know whether it is an openvpn or network issue. Remote Desktop also won't connect.
Would really appreciate some pointers as to where to look, remember that I am self taught and domains are not my strong point!
Thanks
Christopher

Hallo!
I guess almost every Windows Administrator must have got stumped with this question "Where does WINDOWS store a users cached credentials?
Every user who had once logged onto a Server/Desktop while it was connected to the domain could sti…

Log files are useful in diagnosing and repairing problems. This is a list of common log files and their standard locations that I've compiled. While this is not exhaustive, it is a pretty good list that I've found to be useful. I may update it f…

In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …

With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…