Techdivision
asked on
Cannot connect to clients on the network
I'm trying to use RRAS (Remote Web Workplace) to connect to a client on the network. It doesn't work. However, I've forwarded Port 4125 to the server, along with 443, 80, 3389 etc., and I've also run the wizard to 'Allow access to my entire website through the Internet'. Although I get to the 'Which PC would you like to connect to' dialogue, when I select the workstation and click 'Connect', it comes up with 'Cannot connect to the client computer'. I've logged onto the server through port 3389, and used Server Management's 'Connect to a computer on the network' option, and I get through fine to the client, so I know it's not firewalling software sat on the client blocking the connection. The problem lies somewhere in the proxy part of the server, even though I've opened up port 4125 on the router. Any ideas what could be causing this?
See this link for a list of ports you need forwarded from your router to the SBS server:
http://msmvps.com/blogs/bradley/archive/2005/01/21/33537.aspx
Is there any firewall software running on either the SBS server or the PC clients?
http://msmvps.com/blogs/bradley/archive/2005/01/21/33537.aspx
Is there any firewall software running on either the SBS server or the PC clients?
ASKER
No, 444 and 4125 are open (along with a bunch of other ports), and I have a single network card configuration with a Belkin router providing the firewalling, so I can't see where the blockage is. I can also connect onto the client using Terminal Services from within the network, so it's not a client firewalling issue. It's definitely something to do with this proxy, as I can also get onto the server with Terminal Services.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
'Web Services Configuration' is set to 'Allow access to the entire web site'. 'Services configuration' is now set to let everything through except FTP (although it was only configured to allow Skype through, previously). I thought that enabling Terminal Services in Service configuration might solve it, but I'm still getting the same error message, I'm afraid. Can't connect to the Server desktop through the wizard either, even though I can connect to it via Terminal Services!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks chaps, turned out nothing was wrong with the setup - a weekend reboot cured the problem. Typical bloody Microsoft system!
Regards
Steve