Using RWW with SBS 2003

[tmarinoj]

I am a new SBS 2003 user. I've been tasked to be the IT guy for my wifes Mortgage business. They are currently set up with 10 computers, all running XP pro SP2. I use basic XP file sharing for now, and it is working ok, but i think it is time to upgrade them to an SBS 2003 server. It's hard to keep up with all the user names/password on 10 machines especially when new users come into the office which happens quite often. I have just purchased SBS 2003 and have a small network up and running in my house, 1 servers, 1 desktop with XP SP2 and 2 laptops running wireless both with XP SP2.

One thing my wife is very interested in for her business is the RWW capabilities of SBS 2003. I am trying to get this set up at home before I can convince her to make the purchase for the business. I have a few questions about how to set this up.

I know i need to run the wizard in SBS 2003. What else do i need to do besides that.

1. Need to get a domain name, myname.com
2. I believe i need to use some sort of DNS naming service like no-ip.com or dyndns.com.
3. Once i run the SBS2003 wizard, and have my domain name and dns naming service, do i need to do anything else. When i type in https://myname.com, will it take me directly to the RWW login screen? Do I need to do any port forwarding on my router? At home I have a linksys NR041 router and a belkin wireless router set up as an access point connected to the linksys router, wife's office has a sonicwall TZ140W (i think it's the 140). Does my Server need to have a static IP address, if i need port forward than im sure it does? My server is setup to be the DHCP server, i have that function disabled in the router.

I think im on the right track to getting this setup, but i know if im wrong you'll let me know. I have not tried anything yet, don't want to purchase the DNS service until im 100% sure i need it.

Any help/advice would be helpful.

Thanks in advance

Tom

[YeOldeStonecat]

Your server, since it's a domain controller, will need to be on a static LAN IP address. Similar to this article here..screenies from my SBS box at home.
http://www.speedguide.net/read_articles.php?id=1660

First I recommend ditching the troublesome NR0 router..I know it says Linksys on it for a brand, but it's a leftover production run from a super budget white box router they mass produced for an ISP that went belly up...and that "network everywhere" name is their retail outlet method of clearing that stock. It's a very troublesome router. I like Linksys as a brand..just not that series of theirs.

On whatever router you have....you'll forward ports 443 and 4125 to your servers IP. That's all you need.

When running the ICW (internet connection wizard) in SBS...towards the end, you can select "Entire website" in the firewall selection...since you're behind a router.

Make sure your Administrator password is a good one.

Group Policy in SBS will set the proper XPsp2 firewall rules in your workstations. Just make sure users are in the remote web group in ADUC.

You can use it easily from a dynamic dns service...that's how I have mine setup at home....from a remote computer...you'd open up internet explorer...and type in (for example)
https://tmarino.homeip.net/remote
You need the "S" in httpS, and a /remote at the end
Or if you just want to quickly check e-mail...OWA (Outlook Web Access)
https://tmarino.homeip.net/exchange

One note...if you use Internet Explorer 7.0...you will see what appears to be an error relating to a certificate...just select the middle choice to proceed anyways. And add that certificate to your trusted list so it doesn't nag you again.

Some resources for you...
http://support.microsoft.com/kb/833983
http://www.microsoft.com/technet/prodtechnol/sbs/2003/support/2e29ae10-75bf-4fa7-868f-e9e162d4a985.mspx?mfr=true

And a great site you should bookmark if you will be admin'ing an SBS box...
http://www.smallbizserver.net/Default.aspx

[tmarinoj]

Thanks for the reply.

I will take your advice on the Router.

I will be working on getting this working in the next few days.

Thanks for sharing the links for SBS 2003.

I will let you know how everything goes

Tom

[YeOldeStonecat]

I will let you know how everything goes

Tom

Sure thing...good luck...SBS is a great package, enjoy! We'll be here if you need more help...a couple of us here who are familiar with SBS. :nod:

[tmarinoj]

I set this up and everything works great. Thanks. I was able to access my server and Client PC's just fine from a friends house.

I do have one issue though. I would like to be able to access my PC's from work too. I work for tycoelectronics, they have a pretty heafty firewall here. It's tough to do alot of things. I tried accessing my computers from work, when i do so i get to the log in page, and can log in just fine to the RWW page, but when i try to connect to a client PC it times out. Also, when i try to access the intranet site on the server i get the following error

HTTP 502 Proxy Error - The specified Secure Sockets Layer (SSL) port is not allowed. ISA Server is not configured to allow SSL requests from this port. Most Web browsers use port 443 for SSL requests. (12204)
Internet Security and Acceleration Server

Do you know of any way I can get around this. Could i use a different port maybe?

[YeOldeStonecat]

Your employers IT guys probably have outbound 3389 blocked....best to ask them for permission. It's sort of a rule here that we don't aid in bypassing employee/school network rules.

As for your proxy error..is that happening only from your work? Can you access it from another location outside your network?

[tmarinoj]

no problem, i understand.

I will ask them about it, but i don't think they'll make any changes to accomadate me. Im not that important here:)

I have no problem accessing from other computers, issue is only at work. Figured it would have been nice to have access to my home computer from work. I'll just have to go to plan B of using a broadband wireless laptop to access from work.

Do you think I would run into the same problem if i used VPN?

[YeOldeStonecat]

Do you think I would run into the same problem if i used VPN?

If they clamp down on RDC traffic...I'd bet a pint of Guinness they also block outbound VPN traffic.

[koldchillah]

Your employers IT guys probably have outbound 3389 blocked....best to ask them for permission. It's sort of a rule here that we don't aid in bypassing employee/school network rules.

Actually, it's likely outbound port 1425 was getting blocked. If you use RWW to remote into the workstations, the ActiveX control built-into RWW will proxy the RDP traffic over port 1425 out the WAN side. Since regular HTTP & SSL is typically allowed outbound, he would have no problem initially logging into RWW to attempt the RDP session, but would fail to connect if 1425 wasn't allowed out.

[tmarinoj]

Thats exactly what happened, I was able to log into the RWW, but when i tried to attempt the RDP session that is when I had issue.

I got a wireless broadband card which works very very at my work place this has been my way around this.

Thanks again to everyone for there replies