Re: SSL for Companyweb via Internet
- From: "JD" <hampton.jd@xxxxxxxxx>
- Date: 8 Jan 2007 08:50:38 -0800
Steve Foster [SBS MVP] wrote:
Are you sure you have 444 forwarded to the SBS (in the same way as 80 and
443)?
Not entirely, no.
Are you behind another firewall when you try to access this?
No, I'm not.
Is your SBS configured with 1 nic or 2? What's the design of your network
look like?
1 NIC. We have several static internal IP addresses, assigned to
various domain names on the same server..
{all other unassigned IPs} goes to sbserver.mycompany.com
sbserver is set up with port 80 / ssl 443, home directory
c:\inetpub\wwwroot
192.0.0.3 goes to virtual server companyweb.mycompany.com
companyweb is set up with port 80 / ssl 444, home directory
c:\inetpub\companyweb
I also have the header of "link.mycompany.com" with port 8080
associated with it, since originally I wanted companyweb to be
https://link.mycompany.com
192.0.0.14 goes to virtual server link.mycompany.com
link.mycompany.com is set up to port 80, no SSL port, with home
directory redirected to https://link.mycompany.com (I'm trying to get
it to go to the SSL in companyweb)
If it's single nic, then it has to be that you're not port-forwarding 444
properly (as it appears to be working properly internally).
I'm sure that's the case. Can you advise how to do this properly?
Thanks,
JD
.
- Follow-Ups:
- Re: SSL for Companyweb via Internet
- From: JD
- Re: SSL for Companyweb via Internet
- References:
- SSL for Companyweb via Internet
- From: JD
- Re: SSL for Companyweb via Internet
- From: Steve Foster [SBS MVP]
- SSL for Companyweb via Internet
- Prev by Date: Re: Certificate error when logging onto SBS2003 remote web access
- Next by Date: Re: VLANs
- Previous by thread: Re: SSL for Companyweb via Internet
- Next by thread: Re: SSL for Companyweb via Internet
- Index(es):
Relevant Pages
|