Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

After SBS2003 Repair, Companyweb & SPS Sites not available from outside network

Posted on 2008-10-28
3
Medium Priority
?
1,282 Views
Last Modified: 2012-05-05
Good morning!

About a month ago we repaired our SBS 2003 installation after some intermittent NIC connectivity issues. Afterwards, we have been unable to connect to our companyweb site as well as our bottom-level portal sites.

We are operating on a 2-NIC configuration with a SSL certificate from GoDaddy.

OWA & RWW work fine - no issues there.

On the server, and on internal network clients, we can connect to companyweb via https://servername:444/default.aspx without incident (other than a certificate warning since it's a different domain).

From those same clients, however, if we attempt to login via https://domainname.net:444 using Firefox we receive a "Data Transfer Interrupted" error. Using IE7 I receive a "Internet Explorer cannot display the web page" error.

companyweb is using the same GoDaddy SSL certificate that is being used by Default Web Site (OWA / RWW, etc) so I know the certificate is valid and is assigned to a private key.

Please see the attached iis.txt file for my current IIS configuration.

Please let me know if you need any additional information.

Thank you,
Chris
iis.txt
0
Comment
Question by:goodie069
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 16

Assisted Solution

by:BBRazz
BBRazz earned 1000 total points
ID: 22822523
The attached IIS.TXT does not show if the companyweb server has the host header of domainname.net on 444

Thats the first thing I would check.

-BBRazz
0
 

Author Comment

by:goodie069
ID: 22822727
companyweb has a host header of "companyweb" as Default Web Site (running OWA, RWW) has the host header of domainname.net on port 80 - setting both to domainname.net causes a conflict.

Am I missing something?
0
 

Accepted Solution

by:
goodie069 earned 0 total points
ID: 22822925
After changing the IP address on companyweb from the LAN IP on both companyweb and companyweb.domain.local, as well as companyweb for the SSL identity it appears everything is functional again.

I think the issue was with the SSL IP address being a local address instead of All Unassigned.

Thanks for your help!
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

These days socially coordinated efforts have turned into a critical requirement for enterprises.
When using a search centre, I'm going to show you how to configure Sharepoint's search to only return results from the current site collection. Very useful when using Office 365 with multiple site collections.
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

661 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question