Re: Remote Web Workplace - Cannot Connect to Server Desktop, but can use outlook web access, timing out or network error, sbs2003.
- From: "Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Apr 2008 09:35:15 -0500
While you are working on it...
You should absolutely close PORT 80
The only Ports required are
Port 25 for email
Port 443 for SSL (OWA, etc)
Port 444 for SSL on CompanyWeb
Port 4125 for RWW
and if you so desire 3389 for direct RDP
--
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"TR newbie" <nospam@xxxxxxxxxx> wrote in message news:eneHHuTpIHA.548@xxxxxxxxxxxxxxxxxxxxxxx
Excellent work Cris, I had setup the services on the router but I hadn't then inserted them into the firewall rules set.
This router has some predefined common service names and the ports for them, http is 80 and so on. Approx 50 are in the list. In a related window there is a section for creating new services for that list. I thought that just by creating the service that this was enough. It wasn't, it only added these items into the pre-defined list so they could then be selected for the firewall rules. I've since put the 3 items I created into the firewall rules.
I'm off to test if this fixes it, I'm guessing it should. I will reply back here and let you all know.
Thanks very much.
"Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:%23BSUhCOpIHA.548@xxxxxxxxxxxxxxxxxxxxxxx
Have you verified that port 4125 is being passed to the SBS server?
You say you can't connect to the server desktop
What about a workstation?
--
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"Derek" <123123123123@xxxxxxxxxxxxxxxx> wrote in message news:%23t61vXNpIHA.3456@xxxxxxxxxxxxxxxxxxxxxxx
Dear All,
I'm trying to work out why I cannot connect to the server desktop remotely,
but I can see email remotely.
What I can use remotely:
View both server reports,
Use Outlook Web Access,
Download Connection Manager,
What I cannot use remotely:
Server Desktop - times out.
Administer the company's internal website - Loading.... then times out.
Monitor Help Desk - IE cannot display the page after 30+ seconds, time out?
When I try to Connect to Server Desktop I get taken to the correct screen
where I can select the server, then choose the optional settings, and then
click the Connect button. After this I get a security window that says "Do
you trust the computer you are connecting to? ... Do you wish to allow
access to the clipboard? Do you wish to continue.... Yes / No " so I click
yes. Then after about 1 minute or so I get a screen message box telling me
that the connection has timed out.
The screen message is:
VBSCript: Remote Desktop Disconnected
The client could not connect to the remote computer, remote might not be
enabled, the computer might be too busy. It is also possible network
problems... please try again later. if the problem persists please contact
admin.
Router Firewall - uPnP, now manually entered:
Today I was trying to setup the router using the uPnP solution. The
firewall rules in the uPnP table would vanish whenever the router was
updated or that table was refreshed using the router interface, so then
there would be no remote connections of any kind possible. So today I went
through the wizard and manually entered the same rules into the firewall.
The rules remained after I power cycled the router. Everything seemed to
work ok on site, but I don't have another outside connection I can use to
test out the remote functionality, there is only 1 internet router on site.
Is there a way I can test out remote connectivity with only 1 internet
connection?
All I can think of is to leave a pc on at home and try to do a remote
connection to my home pc, and then use that to try to connect to this office
remotely. Any other suggestions?
Other info:
Non Static Internet IP Address - This is being worked-around by using a
dyndns service I setup today, it seemed to be working ok today but after I
got home the IP address changed and this is possibly what is causing the
problem. I can use the mysite.dyndns.org to resolve the ip address, this
works fine. But is this affecting the Certificate?
To get round the mysite.dyndns.org I've pinged the address and entered the
IP manually into the IE and this has not made any difference, still the same
level of access.
Certificate Warning:
I got a warning but I installed the certificate for now. The warning was
like "This certificate is not from the site it was issued by/for. Are you
sure you wish to continue, we recommend you do not continue." - something
like that. I made the certificate earlier during the wizard.
I've tried to connect using a laptop and a desktop I have at home. The
laptop was able to connect while I was working in that office today.
It's SBS2003, a new clean install, came with SP1 on the disks. I've let it
install all the security patches and some of the software ones.
It works fine so long as the IP doesn't change, I think, I couldn't actually
test this when I got home because the IP had already changed! :-(
My theories:
1 - I've missed something on the router firewall setup.
2 - There is a problem with the certificate, and this is causing the auth to
fail/timeout.
3 - Some other authentication is timing out.
4 - There is a service that is not running that needs to be running.
I wish I could test remote services while on site when they only have 1
internet connection, can I do this using some web tool, or do I buy a USB
Mobile Broadband dongle and account for this purpose?
Thanks for reading this, I look forward to all replies.
Regards,
Derek - I'm new to this, please be easy on me.
- Follow-Ups:
- Prev by Date: Re: SPAM in the NG
- Next by Date: Re: New SBS3003 to existing Domain
- Previous by thread: Problems with SBS Premium Upgrade
- Next by thread: Re: Remote Web Workplace - Cannot Connect to Server Desktop, but can use outlook web access, timing out or network error, sbs2003.
- Index(es):