-
Port 80 is forwarded to the server's IP address in the router's UPnP forwarding settings page.
Port 443 is also forwarded to the server's IP address. According to the info I have seen, this should allow http://companyweb access, but it doesn't. The http://companyweb page cannot be accessed at all except on the server itself.
The shared fodleres can be accessed from internal PC's using the \\Servername of course.
I tried a HOSTS file entry, and changing the DNS server settings on the client PC's, but neither of those had any effect.
If anyone knows of any books on VPN and remote acess, and/or DNS for Server/SBS 2003, I'd appreciate the recommendations.
Thanks.
-
The URL http:/companyweb must be replaced by a fully qualified domain name pointing to your "company website". To use port 443 (SSL) you need a PKI security certificate. Most are expensive, but there are a few free alternatives such as OpenSSL. I've found it easier to use SSL for OWA email rather than VPN while traveling.
You must also have public DNS entries pointing to your domain and server.
Here is the response from a dig command for my home domain (minus identifying info).
Code:
06/01/07 20:08:35 dig domain.com @ xxx.xxx.xxx.xxx (this is a public DNS server)
Dig [email protected] (xxx.xxx.xxx.xxx) ...
Authoritative Answer
Recursive queries supported by this server
Query for domain.com type=255 class=1
domain.com A (Address) xxx.xxx.xxx.xxx
domain.com NS (Nameserver) dns1.xxxx.net
domain.com SOA (Zone of Authority)
Primary NS: dns1.xxxx.net
Responsible person: responsible person
serial:2
refresh:3600s (60 minutes)
retry:600s (10 minutes)
expire:86400s (24 hours)
minimum-ttl:3600s (60 minutes)
domain.com MX (Mail Exchanger) Priority: 10 xxx.xxx.xxx.xxx.
domain.com TXT (Text Field)
v=spf1 mx -all
dns1.xxxx.net A (Address) xxx.xxx.xxx.xxx
The above entries are sufficient for running a IIS and Exchange with complete internal and external access. I use Outlook Web Access, FTP and web access using a public computer or my notebook from around the world frequently.
-
Don't you have access to the domain records over the public internet?
This is simple
Setup an A record on your DNS hosting site and setup a forward lookup zone in your internal DNS for your company. You need nothing more. Internal LAN hosts will using the internal DNS for blah.com lookups, and obviously internet users will use whatever is published via records thru your dsn mgmt company (i.e. GoDaddy.com or whatever)
