Remote Access and Outlook Web Access on SBS 2003

[mannuraama]

Hello, we are running a SBS 2003 server with just NIC card connected with D-Link DI-524 router. NIC is connected wired with the router and router is updated to the latest version. Now the problem am facing is I cannot connect to the server for Outlook Web Access or Remote Access though the open ports for 443, 444, 1723, and 4125 in the router is enabled to go to the server (locally at 192.168.0.2) from the router. I’m also unable to connect to the router.

I don’t think the duality of local subnets is cause of the problem because my local IP is 172.16.0.34. The ISP is a fixed-IP T1 line, and the DNS and Gateway entries are correct. Before you guys suggest I’ve also re-run CEICW, even turned off turning off and then turned on access but still the same problem.

Can anyone here help me out of this? Many thanks.

[mannuraama]

Opps, sorry I did some mistake I guess. Actually the “My Local IP” is on my home office. and the Dlink is at another location who’s IP is 192.168.0.1, and the SBS 2003 server is on its subnet at 192.168.0.2. And here is the problem. When I try connecting from my home office to the external IP of the server's office it wont allow me to connect the server, though I was able to connect to the D-Link router.

[Amadeus]

Well I don’t think your Windows or SBS server is the cause of this issue in anyway. Even I don’t like to have 2 NICs in a domain controller but regarding your issue I don’t think your d-link is a real firewall. You might need to consider upgrading this to something more robust. Apart from this I guess you have double NAT in place. both 192.168.0.0 and 172.16.0.0 are private/no routable networks. Just check your Dlink, I fit is doing NAT, call up your ISP and tell them to disable NAT on their router.

[mannuraama]

Thank you very much for the help Amedeus, As I am not at my client's location now, this is extrapolated from what I remember:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : unknown
Description . . . . . . . . . . . : unknown
Physical Address. . . . . . . . . : unknown
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 66.205.225.9
66.205.225.10
Lease Obtained. . . . . . . . . . : Sunday, February 05, 2006 11:43:31 PM
Lease Expires . . . . . . . . . . : Monday, February 06, 2006 12:43:31 AM

[ComputerRick]

First, I agree with Lanwench about it being a configuration issue with your DLink. The reason I'm saying this, if you want to resolve your problem, is because you're so intent on blaming the MS OS.

IF it works in the office, and you're using a single NIC, IT IS NOT the server configuration.

Second, to effectively test your configuration on your DLink, go to the Advanced Tab, Click on the DMZ button and enter the server address.

My concern is that you entered the information in only 1 of the 2 required locations to make it work. The Advanced | Firewall section, where you need to be sure that it is allowed through, and the Advanced | Virtual Server section, which is actually the port forwarding.

Based on the information you've given in the forum, It's very unlikely that it is any issue related to the server at all. It's the DLink, and that is reinforced by the fact that you can access OWA on the local side, you can manage the DLink on the WAN side, but you can't cross the DLink to get internal.

Good Luck.