Olaf, It will not connect from the Homeserver desktop running RDP to the workstation in question. That was the one direction I didn't test. Any ideas what could be causing this?
I can connect from the homeserver desktop via RDP to other machines on the network and other machines can connect to the workstation in question via RDP. It is something between the outbound WHS and the inbound RDP of the machine in question.
Its not the firewall on the machine. That port has been tried as open and closed. Regards from Boston. Hello, a few more questions to narrow down the issue: What for an error message do you get exactly, if you try to establish the Remotedesktop session? Are there any signs in the event log of the client, that a connection attempt has been made (including security log)? What is the status of the Windows Firewall/Internet Connection service?
May 3, 2014 - Also, if you're trying to access a remote PC with a local Mac, first download. While Window's RDC only works on some OS editions and requires a. Initial setup, and grant it access to the various permissions it asks for like.
![Via Via](/uploads/1/2/5/5/125501521/590813237.png)
Does it work, if already a user is logged on? Is there a difference in the Service Pack level between the functioning and the non functioning system? Best greetings from Germany Olaf.
Njk18 wrote: Olaf, It will not connect from the Homeserver desktop running RDP to the workstation in question. That was the one direction I didn't test.
Any ideas what could be causing this? I can connect from the homeserver desktop via RDP to other machines on the network and other machines can connect to the workstation in question via RDP. It is something between the outbound WHS and the inbound RDP of the machine in question. Its not the firewall on the machine.
That port has been tried as open and closed. Regards from Boston.
Norm I agree it's unlikely to be a firewall issue, as I already posted before Could be name resolution issue. Instead of entering computer name of the client try entering the client IP address in the computer name field, for example 192.168.1.6 If this also fails the next suspect is your router (have a look at firewall / port forwarding settings, or try another router). If it works with the client IP address is a possible workaround. Also rebooting both the router and server could do the trick. I am going to suggest, as a practical matter, that you may find it faster to rebuild the workstation that you're having problems with at this point. Your problem has the feel, to me, of a permissions issue of some sort.
I really don't believe that it's a hardware issue, and I don't think that it's a firewall or name resolution issue either. Permissions issues can usually be worked out given enough time and some dedication, but it may take quite some time to track down. If you don't have the time to invest, nuking the workstation and reinstalling everything may take less time.
And it gives you an opportunity to eliminate any software you're not using any more. I believe you've said you have backups; I would make a pass through the drive(s) in the workstation and just copy everything I thought I really couldn't live without to an external drive, as an insurance policy. (Well, okay, I probably wouldn't personally; I don't think I have a free external drive right this instant. But I would recommend it if you have an external drive with that much free space. ) Then I would pave the workstation over.
Maybe you could put Vista on it, if you've been thinking about giving Vista a try? Ken, Thanks for your thoughts.
I did build an XP SP2 clean install with just the drivers and the connector. I turned off the built in firewall and got the same results. So I restored the original system from WHS Backup.
I'm afraid to use Vista - I haven't heard much good about Vista. Whenever I call for tech support from Dell their techs all shy away from Vista. I'm open to other thoughts, but its gotta be a permission I haven't seen. If there is anyone on the WHS team, I'd appreciate hearing from you. This machine has always had XP Pro, right? Have you ever been able to connect through the Remote Access web site or otherwise from the server?
Something you could try: If you've got a spare network card (PCI) try disabling the current NIC in the workstation having problems and installing/configuring the spare. Vista: there are a lot of good things to say about it. And there are a lot of bad things to say about it. For my purposes, the good outweighs the bad, but I'm not saying you should try it just on my say-so. I was observing that this could be an opportunity to try it if you want to. Njk18 wrote: I did build an XP SP2 clean install with just the drivers and the connector.
I turned off the built in firewall and got the same results. So I restored the original system from WHS Backup. I'm afraid to use Vista - I haven't heard much good about Vista. Whenever I call for tech support from Dell their techs all shy away from Vista.
I'm open to other thoughts, but its gotta be a permission I haven't seen. If there is anyone on the WHS team, I'd appreciate hearing from you. Did you ever look into the event log of the client, as asked? If a connection is tried, but refused, you would see an appropriate event here. Are there NVidia drivers installed? I think there was an issue with certain NVidia software components and RDP, but can't nail it down. About XP and Vista - I dont use XP any longer on my own workstations.
If the system is powerfull enough, Vista is not too bad and has it's benefits. And support techs are a bunch of conservative folks - the old stuff they know, the new stuff is still unknown and undocumented.
![Mac still asks for permission when trying to access via remote desktop windows 10 Mac still asks for permission when trying to access via remote desktop windows 10](/uploads/1/2/5/5/125501521/765688221.png)
Best greetings from Germany Olaf. Olaf, The response to your suggested tests in bold Which is the DNS server shown for your server? Correct external DNS. Now enter the name of your missing workstation.
Do you get the proper IP address or a false result or nothing? Shows external DNS, can't find ip address of all local machines, even those that works through the home server web front end.
Workstation that is having problems is listed in etc hosts Type exit to leave the nslookup prompt. Ping your workstation by name.
Does the proper IP address respond? Yes nbtstat -A IPAddress gives also the expected results back?