<div>
You need to have whomever hosts your mydomain.com to set up your DNS as follows:<br />
Your public IP = 99.66.88.77<br />
<br />
DNS A Record for: remote.mydomain.com with IP 99.66.88.77<br />
<br />
Sonicwall: WAN = 99.66.88.77<br />
&nbsp;Ports forwarded:<br />
&nbsp; 443 HTTPS<br />
&nbsp; 25 SMTP<br />
&nbsp; 987 SharePoint<br />
&nbsp; 1723 PPTP VPN (optional).<br />
<br />
80 is not recommended nor needed as it redirects to HTTPS 443 anyway. Less is more in this case.<br />
<br />
Philip
</div>


<div>
the first wizard: Setup your Internet addres.<br />
The default url is:<br />
<br />
<a href="https://remote.yourdomainname.com/remote" rel="ugc">https://remote.yourdomainname.com/remote</a><br />
<br />
the only port you need to forward on your sonicwall is port 443, to your SBS server.<br />
more info can be found here:<br />
<a href="http://sbs.editme.com/sbs2008rww" rel="ugc">http://sbs.editme.com/sbs2008rww</a>
</div>


<div>
what happens when you put in <a href="http://" rel="ugc nofollow">http://</a>[ipaddress]/remote?
</div>


<div>
then you'll have certificate issues.<br />
but you cAn change the remote:<br />
<a href="http://www.sbstraining.net/post/2009/01/SBS-2008-remotedomain-prefix.aspx" rel="ugc">http://www.sbstraining.net/post/2009/01/SBS-2008-remotedomain-prefix.aspx</a><br />
<br />
but, the easy part is what philip said:<br />
DNS A Record for: remote.mydomain.com with IP 99.66.88.77<br />
this needs to be set at your domain name dns holder.
</div>


<div>
&quot;<a href="http://" rel="ugc nofollow">http://</a>[ipaddress]/remote?&quot;<br />
and btw, it's ALWAYS httpS, NOT http, you DONT want anything over port 80.
</div>


<div>
I had my Hosting create the DNS record from my remote.mydomain.com<br />
The sonicwall is setup correctly with the correct ports and I had the sonicwall support test it.<br />
<br />
This is what I get if I type IP/remote<br />
404 - File or directory not found.<br />
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
</div>


<div>
when you ping remote.mydomain.com, do you get a reply from your external IP?<br />
so you are 100% sure port 443 is FORWARDED to your SBS internal ip?
</div>


<div>
If i look in IIS for the the remote website and I right click on SBS Web Applications and select site bindings, I see remote.mydomain.com but the port is 80, IP is *<br />
and https has no host name with port 443
</div>


<div>
that is ok, no need to change things manually.
</div>


<div>
Yes I can ping remote.mydomain.com and get my static IP.<br />
Yes 443 is forwarded to the server. I am calling again right now to have them verify.<br />
I can telnet remote.mydomain.com 80 but not 443<br />

</div>


<div>
you should be able to do that on port 443, so it's a firewall issue on your sonicwall<br />
btw, close port 80
</div>


<div>
I can telnet IP 443<br />
Is that a reverse DNS issue?
</div>


<div>
actually not, that is just a dns issue.<br />
if you can ping the remote.mydomain.com you should be able to telnet into the remote.mydomain.com.<br />
are you testing this from an external client?
</div>


<div>
Ok this is really strange. I have remoted into 3 outside computers and tested opening IE and going to remote.mydomain.com with https<br />
1 I get the strange login box asking for level 15 like in my original post<br />
2 I get Internet Explorer cannot display the webpage <br />
3 it works!<br />
<br />
I am puzzled!
</div>


<div>
Security settings in your IE, Add-ons are both.<br />
<br />
Reset your IE: Tools --&gt; Internet Options --&gt; Advanced --&gt; Reset.<br />
<br />
Close all browser windows and try again.<br />
<br />
Make sure your RWW sites are in your Trusted Sites list.<br />
<br />
Philip
</div>


<div>
then I guess that firewall is nor forwarding port 443 correclty.<br />
btw, make sure the remote clients have their firewall/antivirus disabled for testing.<br />
your are using IE7 on the clients?<br />
can you give me a screenshot of that error 15 please?
</div>


<div>
The level 15 error only happens if I forget to add S to HTTP.<br />
I reset IE settings and still nothing<br />
I have disabled all firewall/virus software and still nothing.<br />
Yes they are all IEy7 even the one that can get through.
</div>


<div>
ah, okay, so we can ignore the error 15, you only need to connect with httpS.<br />
actually, since one can get through, the rww is fine I think.<br />
If you are getting ' cannot display the webpage', there is a problem with access to port 443.<br />
actually, when one client cAn get through, port 443 will be forwarded and rww will run fine, I've never seen port 443 to open and close by itself so that will be fine.<br />
So we'll need to focus on the clients here I think.<br />
can you telnet with the problem client to port 443?<br />
give us some screenshots too please.
</div>


<div>
I have over 10 computers I have tested outside and only one is ok to connect.<br />
<br />
I can't telnet 443<br />
Only on the working computer.
</div>


<div>
hm, if this is only one pc, is the firewall blocking certain ip's?<br />
maybe that ip/range is allowed on the sonicwall to connect through port 443?<br />
this must be a firewall issue if it's only one client/10 that can connect.
</div>


<div>
Sonicwall is way over my head and I have called them 3 times today because I too think it is the firewall. What should I tell them? they go in and test it out and can see that prot 443 is going through.
</div>


<div>
Ok long phone call with sonicwall<br />
they can get through with the ip but not by name. they were testing packets through the different ports. So the packets never arive at the firewall if the remote.mydomain.com is entered.<br />
Only if the IP is typed
</div>


<div>
netstat -an &gt;c:\Ports.txt on the server from an elevated command prompt.<br />
<br />
Open Ports.txt with Notepad and search for 443.<br />
<br />
Should see:<br />
&nbsp; TCP &nbsp; &nbsp;0.0.0.0:443 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0.0.0:0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;LISTENING<br />
&nbsp; TCP &nbsp; &nbsp;192.168.40.254:443 &nbsp; &nbsp; 192.168.X.X:XXXX &nbsp; ESTABLISHED (SBS IP and 4xxx port or so)<br />
&nbsp; TCP &nbsp; &nbsp;192.168.40.254:443 &nbsp; &nbsp; 192.168.X.X:XXXX &nbsp; ESTABLISHED (SBS IP and 4xxx port or so)<br />
&nbsp; TCP &nbsp; &nbsp;[::]:443 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [::]:0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; LISTENING<br />
<br />
Philip
</div>


<div>
I replaced the sonicwall with a basic linksys to see if that was it. Nope.<br />
I did find this cool article from microsoft<br />
<a href="http://support.microsoft.com/kb/290051" rel="ugc nofollow">http://support.microsoft.com/kb/290051</a><br />
I can't even do a tracert <a href="http://www.microsoft.com" rel="ugc">www.microsoft.com</a>&nbsp;-d inside the network. it says unable to reslove target system name <a href="http://www.microsoft.com" rel="ugc">www.microsoft.com</a><br />
anyclues as to what to look for in my server
</div>


<div>
might be some kind of dns problem.<br />
did you change anything manually on the SBS server, escpecially in the dns mgmt console?<br />
did you try running the internet wizard again, followed by the 'fix my network wizard'?<br />
<a href="http://sbs.editme.com/sbs2008FMCW" rel="ugc">http://sbs.editme.com/sbs2008FMCW</a>
</div>


<div>
WOW I can access remote.mydomain.com from anywhere outside.<br />
Must have been after I called my ISP and complained, even though they say they have an open pipe.<br />
But know I can't get Outlook configured to access remote.mydomain.com.<br />
The users can access though the webpage but not through outlook. And yes I did setup the proxy server settings.
</div>


<div>
I noticed on the computer that can't connect that under connect using SSL only that it says:<br />
Mutually authenticate the session when connecting with SSL<br />
Principal name for proxy server:<br />
msstd:remote.mydomain.com<br />
<br />
I have my own network and use Outlook to connect to my exchange and under connect using ssl only it says:<br />
only connect to proxy that have.... wait! this is because I have 2007 and the other user has 2003<br />
sorry<br />

</div>


<div>
If using the SBS self-issued certificate you need to put the zipped certificate package onto a USB flash drive and install it on the remote machine. Outlook Anywhere functionality will work from there.<br />
<br />
Philip
</div>


<div>
well now I can't get to the webpage remote.mydomain.com. It was working 10 mins ago. 
</div>


<div>
the outlook anywhere guide is here:<br />
<a href="http://technet.microsoft.com/en-us/library/cc794265.aspx" rel="ugc nofollow">http://technet.microsoft.com/en-us/library/cc794265.aspx</a><br />
but make sure the cert is installed and trusted on the remote client(s).
</div>


<div>
and btw, that whole guide is on the rww page:<br />
&quot;How do I use Outlook Anywhere?&quot;<br />
<br />
&quot;well now I can't get to the webpage remote.mydomain.com. It was working 10 mins ago. &quot;<br />
is the ISP modem forwarding ALL ports to your firewall?<br />
make sure the ISP modem isn't blocking any ports.<br />
still using <a href="https://remote.yourdomain.com/remote?" rel="ugc">https://remote.yourdomain.com/remote?</a>
</div>


<div>
I think I am just going to use the IP. The IP works but not the name. I can ping the name and it resolves to the correct static ip. same with an nslookup. So the DNS is routing the name right. NO DNS errors in the server but it is sounding like a DNS issue in the server.
</div>


<div>
Screenshots of the proper bindings in IIS are here:<br />
<a href="https://www.experts-exchange.com/questions/24047757/SBS-2008-and-II7-After-uninstalling-MS-Forefront-security-the-default-website-and-the-SBS-web-applications-are-on-the-same-ports-and-only-one-of-them-will-start-at-the-same-time.html" rel="ugc">https://www.experts-exchange.com/questions/24047757/SBS-2008-and-II7-After-uninstalling-MS-Forefront-security-the-default-website-and-the-SBS-web-applications-are-on-the-same-ports-and-only-one-of-them-will-start-at-the-same-time.html</a><br />
<br />
All resolutions for Web requests are done by Host Header. In this case, remote.mydomain.com is the Host Header. If IIS does not know this, then the request to that URL will not resolve to anything.<br />
<br />
Philip
</div>


<div>
<div class="content wysiwyg-content">
What wizard configures RWW.<br />
I can't get to remote.mydomain.com.<br />
Do I use the Setup your Internet addres and then use remote.mydomain.com or just mydomain.com?<br />
I can get to RWW inside the network but not outside. I just got off the phone with my sonicwall support and they tested all ports and the correct ports are going though to the server.<br />
<br />
If I use remote.mydomain.com from outside it pops up with a login box saying:<br />
The server remote.mydomain.com at level 15 access requires a username and password.<br />
<br />
I tried to use my username and password or the administrator account and still couldn't get in.<br />
If I type just the Static IP I get this werid IIS webpage with a bunch of different languages around IIS.<br />
<br />
Anything else I need to look into?
</div>
</div>


What wizard configures RWW.
I can't get to remote.mydomain.com.
Do I use the Setup your Internet addres and then use remote.mydomain.com or just mydomain.com?
I can get to RWW inside the network but not outside. I just got off the phone with my sonicwall support and they tested all ports and the correct ports are going though to the server.

If I use remote.mydomain.com from outside it pops up with a login box saying:
The server remote.mydomain.com at level 15 access requires a username and password.

I tried to use my username and password or the administrator account and still couldn't get in.
If I type just the Static IP I get this werid IIS webpage with a bunch of different languages around IIS.

Anything else I need to look into?

SBS 2008 RWW. How to set it up.

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).