We are running RD Gateway allowing users to connect to their office PCs remotely. The service has stopped connecting to client computers in the last couple of days however I can still successfully connect to servers using the same method. So, the gateway itself is working and attempting to make the connections but something else must be preventing connections through to PCs. When connecting to a PC remotely we simply enter the NetBIOS name of the destination system, ensure the RD Gateway settings are defined in the RDP connection properties (desktop.mydomain.com) and it usually works perfectly, however not at the moment. I have tried using the IP of a target PC and this doesn't work either, whereas this would work in the past.
When attempting to connect, I get a username/password prompt from the RD Gateway and the connection fails around 10 secs later with a message "Remote Desktop can't find the computer MYPC. This might mean that MYPC does not belong to the specified network. Verify that the computer name and domain that you are trying to connect to."
All of the client-side credentials and settings are exactly the same as they were when the service worked a few days ago so I'm trying to identify what it is server-side that is preventing successful connections. Bearing in mind that the RD connection works fine to a server the issue may lie somewhere with DHCP/DNS specific to PCs on the LAN (PCs use DHCP whereas server IPs are statically assigned).
Any ideas on tracing the source of the problem?