Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Connection SBS 2003 R2

Status
Not open for further replies.

Pictman

IS-IT--Management
Aug 28, 2008
60
GB
I have followed all recommended steps in setting up remote access to my SBS 2003 server including making a setup disk. I cannot get access remotely either using the shortcut set up by the remote setup disk or by any other means. I get an error code 800. Any ideas?
 
Me again re: the above - I can ping the server and the server can ping the remote.
 
What exactly are you trying to accomplish? Are you trying to use remote web workplace or are you trying to establish a VPN connection to the SBS server using RRAS?
 
Normally to allow remote access, all you have to do is open up ports 443 and 4125 on the firewall to the server and have them go to in order to access their desktops.

If you want them to be able to map drives from home computers to your server, then you'd want to set up a VPN, and that requires separate ports to be open. The setup disk isn't actually very important. It just makes it easier for end-users that don't know what your server's name is.

Dave Shackelford
Shackelford Consulting
 
Thanks for that - how do I open port 4125? I'm currently using the firewall on SBS.
 
Are you running ISA then? If not, does your server have a private IP, or a public IP address when you do an "ipconfig"?

I think you could figure out how to allow TCP 4125 on the server firewall if you aren't running ISA. If you have some other device like a broadband router, you'll need to open TCP 4125 there too.

Dave Shackelford
ThirdTier.net
 
No - I'm not running ISA. Server has a static IP address.

The firewall on the broadband router is disabled. I've run netstat and discovered that 4125 is not listed.

Additionally, my LAN router is configured 192.168.16.2. I can't get access to the GUI of the router. Putting 192.168.16.2 into a browser takes me to a server interface. 192.168.16.1 gets nowhere.

Hugh
 
Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix:
Description: Intel <R> PRO/1000 MT Dual Port Server Adapter
Physical Address .:**-**-**-**-**-CD
DHCP Enabled . . . : No
IP Address . . . . : 192.168.16.2
Subnet Mask . . . .: 255.255.255.0
Default Gateway . .:
DNS Servers . . . .: 192.168.16.2
Primary WINS Server: 192.168.16.2

Ethernet adapter Network Connection:

Connection-specific DNS Suffix:
Description: Intel <R> PRO/1000 MT Dual Port Server Adapter
Physical Address . : **-**-**-**-**-CC
DHCP Enabled . . . : No
IP Address . . . . : 192.168.1.2
Subnet Mask . . . .: 255.255.255.0
Default Gateway . .: 192.168.1.1
DNS Servers . . . .: 192.168.16.2
Primary WINS Server: 192.168.16.2
NetBIOS over Tcpip : Disabled
 
Go into Control Panel. Windows Firewall. Exceptions, Add PORT. 4125.

You should have TCP 443, 4125 open and possibly 80 if you are publishing any web pages. Also UDP 123 (time service).

I would recommend you figure out your external firewall/router and make sure that your public IP is NATed over to your internal address of 192.168.16.2, otherwise none of this will work from the outside.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
markdmac is right on the ball...configure windows firewall to allow the ports to open...I am not a big fan of windows firewall...symantec client 3.1 works well...
 
Have you run the Internet and email config wizard in the server management console ?

If not, you need to run this. Even if you have run it before, if you want to use anything IIS based then you will need to run it again and tick the right boxes.

Bobby
 
make sure that your public IP is NATed over to your internal address of 192.168.16.2, otherwise none of this will work from the outside

I may be having a brain fart here, but the public IP needs to be natted to the external card 192.168.1.2 rather than the internal 16.2 ?
 
Yes you need to NAT from the Public IP to the NIC used to provide an Internet connection on the server.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top