- Is your SME box "Virgin", or do you have any contribs or other packages loaded?
- Does your branch office have its own Internet connection, or does it connect through the Head Office?
A. Internet <---> Head Office <--cisco--> Branch Office <---> Internet?
or
B. Internet <---> Head Office <--cisco--> Branch Office?
Are you talking about connecting to https sites at the Head Office, or on the rest of the Internet?
If you're using configuration B. above, and the problem is with https hosts in the "Internet" zone, try turning off the HTTP Proxy on the SME box and see what happens - (server-manager / Proxy Settings / HTTP Proxy status ==> disabled)
If the problem is with https sites in the "Head Office" zone, are you accessing them using "private" IP numbers or (assuming configuration A) through the Internet? (Check the actual IP address returned by "nslookup ...")? Are you accessing them using virtual domain names?
Are there any other firewalls, proxies, or other servers or devices involved?
Try giving us a specific example, something like this:
Branch Office:
- Win XP wkstn, IP 192.168.1.x
- Cisco router
- LAN IP: ???
- WAN IP: ???
Head Office:
- Cisco router
- WAN IP: ???
- LAN IP: 192.168.2.x
SME Server
- LAN IP: 192.168.2.y
- WAN IP: ???
sample non-functioning https site:
https://www.citibank.comError received:
(describe behavior of erroring Win XP system from Branch Office)