Mentiroso
asked on
Remote Access Problems - No Connection
I am trying to connect to a 2003 Windows Small Business Server from my vista machine and I keep getting "This computer can't connect to the remote computer". I have also tried on a Windows XP machine just to make sure the client was not the problem and the same thing happens. I am logging in using the admin l/pw which does have dial in permissions allowed. The server is set up for RAS and it shows to be running on the server. It is connected to a bellsouth (2wire I think) modem directly, not through a firewall. I am lost at this point. Anyone know what I am missing? This is a dial in connection not VPN btw. I tried a vpn connection as well and it failed with error 800. I am connecting by IP address which has been triple verified so that is correct.
Patience, my friend.
I'm trying to understand the scenario. So you're outside the firewall and dialing into the SBS box via RAS, then attempting to RDP to the SBS box?
If this is the case, can you RDP to the SBS box from inside your network successfully?
Can you ping the SBS box when dialed in remotely?
I'd get that box behind a firewall for security reasons. . .
I'm trying to understand the scenario. So you're outside the firewall and dialing into the SBS box via RAS, then attempting to RDP to the SBS box?
If this is the case, can you RDP to the SBS box from inside your network successfully?
Can you ping the SBS box when dialed in remotely?
I'd get that box behind a firewall for security reasons. . .
ASKER
Well I meant to say router, not firewall in my original post. The modem it is hooked into does have a software firewall running.
I am just trying to dial into the server from outside to make changes here and there using RDP. It has been allowed on the server. I also tried a normal VPN just because I thought the RDP was screwed up. Both failed. So after checking the server again and verifying that it had remote desktop connections allowed along with RAS running, I am still lost. I forwarded port 3389 to my server as well and still nothing.
I am just trying to dial into the server from outside to make changes here and there using RDP. It has been allowed on the server. I also tried a normal VPN just because I thought the RDP was screwed up. Both failed. So after checking the server again and verifying that it had remote desktop connections allowed along with RAS running, I am still lost. I forwarded port 3389 to my server as well and still nothing.
Can you RDP into the SBS box from your internal network?
Can you ping the SBS box from outside your network when connected through RAS?
Can you ping the SBS box from outside your network when connected through RAS?
ASKER
I cant make the connection through RAS at all from outside. I am going to the office in a bit to check to see ifI can RDP from internal. I can ping the server from outside though.
It sounds like you're pinging your modem's software firewall.
But I'm lost - you say you're trying to dial in, using a physical 56k modem? And that modem is directly hooked to the server?
I would try to do a VPN through the software firewall - open port 1723 on the modem's firewall and point it to the server.
But I'm lost - you say you're trying to dial in, using a physical 56k modem? And that modem is directly hooked to the server?
I would try to do a VPN through the software firewall - open port 1723 on the modem's firewall and point it to the server.
ASKER
I am on a cable connection at another office trying to access the server. I dont really want to do a vpn connection because I am trying to access software only installed on the server and run it from my other office so I can make changes to a database. That is why I was going with a remote desktop connection instead of vpn.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will look at setting up the remote web workplace. I am new to working with remote access/vpn so I appreciate the info. I will try this out first thing in the morning and get back with hopefully a success story!
ASKER
One question, I have been reading up on RWW and noticed that microsft says to connect using https://FQDN/remote (as an example). Do you have to use a fully qualified domain name or can you use an ip address instead like https:111.111.111.111/remote instead?
You could use an IP. But the FQDN is easier for your users to remember. No reason not to setup something, even if you have a dynamic and need to use a service.
The issue is generally that you need to properly install the self-signed certificate in order for RWW to work from Vista. See this SBS Blog post for instructions:
http://blogs.technet.com/sbs/archive/2007/04/10/installing-a-self-signed-certificate-as-a-trusted-root-ca-in-windows-vista.aspx
Jeff
TechSoEasy
http://blogs.technet.com/sbs/archive/2007/04/10/installing-a-self-signed-certificate-as-a-trusted-root-ca-in-windows-vista.aspx
Jeff
TechSoEasy
ASKER
Yea, I might just register the name, a website was going to be in the works in the next few months anyway.
Thanks guys. I will be trying this out tomorrow!
Thanks guys. I will be trying this out tomorrow!
The best reason for registering a domain name is to be able to use it for your own email. Since it only costs a few dollars a year, there's really no reason to.
But either way, you need to have the certificate match. So rerun the Configure Email and Internet Connection Wizard (CEICW -- which is linked as Connect to the Internet in the Server Management Console > To-Do List) and make sure that your external IP address (if that's what they are going to use for now) is entered in the SSL certificate screen. You can then run it again once you have a FQDN to enter.
A visual how-to for the CEICW is here: http://sbsurl.com/ceicw
Jeff
TechSoEasy
But either way, you need to have the certificate match. So rerun the Configure Email and Internet Connection Wizard (CEICW -- which is linked as Connect to the Internet in the Server Management Console > To-Do List) and make sure that your external IP address (if that's what they are going to use for now) is entered in the SSL certificate screen. You can then run it again once you have a FQDN to enter.
A visual how-to for the CEICW is here: http://sbsurl.com/ceicw
Jeff
TechSoEasy
ASKER