Re: Remote access to SBS2003
- From: "Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Fri, 27 Jan 2006 09:10:26 -0600
Hi Neil,
It's not hard to get confused over a couple of 'remote access' terms.
There are 3 different ways to remotely access the server and it's resources.
These methods *don't* require the remote connection disk, and all 'User'
accounts have permission to use them.
a) Outlook Web Access - http://FQDN/exchange - connects you to your mailbox.
b) Remote Web Workplace - http://FQDN/remote - connects you to your mailbox,
and additional features such as access to computers and your sharepoint
site.
c) Outlook RPC/HTTP - a method of directly connecting Outlook 2003 client to
your Exchange mailbox.
These methods require Adminstrative level accounts:
a) RWW gives you access to server destops for remote administration.
b) RDP (Remote Desktop Connection) gives you direct access to the SBS
server, if you have port 3389 open.
This method requires either Administrative level accounts, or 'Mobile User'
level account.
a) VPN connection.
It is this last connection type that you are trying - and it's not at all
required for anything other than a VPN connection. None of the preceeding
remote access methods require the connection disk, VPN, or the Mobile User
account.
Regarding the certificate - it's important that the certificate name be
entered correcly.
If you have a fixed ip address of 123.456.789, then you enter exactly that
for your certificate name. When you connect remotely, you use
http://123.456.789/exchange or /remote to access either Outlook Web Access
or Remote Web Workplace.
If you have an A record like mail.domain.com that resolves to 123.456.789,
then you can use mail.domain.com for the cerificate name, and use
http://mail.domain.com/exchange or /remote to access the server.
If your certificate is named mail.domain.com and you use
http://123.456.789/exchange to access the server, then there is a mismatch.
That is to be avoided.
Hope that helps.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"Neil" <Neil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D433145F-1995-4F69-8337-AACAE7D48209@xxxxxxxxxxxxxxxx
>I can not seem to access my server at the office from home. I am running
> SBS20032 premium. I have run the internet connection wizard many times, it
> completes without errors. I have run the remote access wizard and it
> completes fine. I have made the remote access disk and carried it home.
> When
> I install it it seems to install fine. When I run it to start the
> connection
> process it instantly times out with an error (I think it is 810) it just
> keeps cycling until I stop it. I can ping the router fine, I can even log
> into the router from home. I have opened the appropriate ports 443, 80,
> 444,
> 4125, 25, 3389, 1723. I thought that it was something on my end at home or
> the ISP that I use but I am able to provide remote assistance to friends
> on
> XP Pro.
>
> I have seen an error about a certificate, perhaps that is the problem,
> when
> running the Internet connection wizard it asks if I am going to provide a
> certificate or use one from someone like verisign, I choose to provide it.
> Do
> I need to somehow add this to the disk that I carry home? Would this not
> be
> part of the disk creation process?
>
> Any help with this would be greatly appreciated.
>
> Thanks
.
- Follow-Ups:
- Re: Remote access to SBS2003
- From: Neil
- Re: Remote access to SBS2003
- Prev by Date: Re: Configuring Internet E-mail
- Next by Date: Re: SBS 2003 Network Bridge
- Previous by thread: Outlook access problems over VPN
- Next by thread: Re: Remote access to SBS2003
- Index(es):
Relevant Pages
|
