Hi,
I've ran my home server Windows 7 Pro for over 2 years now. I run a DDNS on my router, and remote desktop RDP to my server to access it while I'm away. About 3/4 weeks ago I noticed it would only work for an hour or so after a reboot. Following this I wouldn't be able to connect.
I found an online telnet test and attempted a telnet attempt to my DDNS host name and port 3389 for RDP and the connection seems to reach the server, but the error is that "The server is actively refusing the request"...? I have no idea why. The only changes I've made are probably the odd Windows update..
My port forwarding configuration on my router is correct. And my DDNS hostname is working perfectly. Remote Desktop is activated on my server, it's not reset itself or anything. Like I say straight after a reboot it works. Then not too long afterwards the server refuses my attempts. I've tried turning Windows 7 firewall off completely to check there is no dodgy rules and no luck with that.
The server is definitely reachable with or without my DDNS because I can still access my FTP server on my custom port. Could something be blocking or interfering with 3389? How and why might that happen.
Any advice is appreciated I'm pretty lost with this one - I'm having to use Team Viewer for now and it's a right ball ache.
I've ran my home server Windows 7 Pro for over 2 years now. I run a DDNS on my router, and remote desktop RDP to my server to access it while I'm away. About 3/4 weeks ago I noticed it would only work for an hour or so after a reboot. Following this I wouldn't be able to connect.
I found an online telnet test and attempted a telnet attempt to my DDNS host name and port 3389 for RDP and the connection seems to reach the server, but the error is that "The server is actively refusing the request"...? I have no idea why. The only changes I've made are probably the odd Windows update..
My port forwarding configuration on my router is correct. And my DDNS hostname is working perfectly. Remote Desktop is activated on my server, it's not reset itself or anything. Like I say straight after a reboot it works. Then not too long afterwards the server refuses my attempts. I've tried turning Windows 7 firewall off completely to check there is no dodgy rules and no luck with that.
The server is definitely reachable with or without my DDNS because I can still access my FTP server on my custom port. Could something be blocking or interfering with 3389? How and why might that happen.
Any advice is appreciated I'm pretty lost with this one - I'm having to use Team Viewer for now and it's a right ball ache.
My Computer
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- HP Microserver
- OS
- Windows 7 Ultimate OEM x64
- Memory
- 8 GB DDR3 RAM
- Hard Drives
- x5 2TB Hard Drives
(x4 are the same brand)
(5th one is a different brand added where the optical drive is)
- Antivirus
- Windows Defender (Ex AV was Avast)
- Browser
- Chrome