Re: Unable to create secure cert for https OWA - Re-submission
- From: "Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Sun, 5 Feb 2006 09:56:57 -0600
Ok, my bad assumption.
It's a single nic SBS, and the network has been configured to fit the
routers lan ip. Perhaps not the way I'd chose to do it, but it's not an
invalid configuration. Does the CEICW complete without errors?
Did you set that 192.168.0.5 IP address during SBS setup, or change it at
some later time?
I'd guess that the uninstall of IIS, Exchange, and Companyweb and subsequent
re-install has resulted in some inconsistencies, at least between IIS and
the registry. For example, the 'inheritance' error in icwlog.txt referring
to companyweb :
The problem should be caused by the Registry path for Sharepoint doesn't
match the Companyweb Identifier value in IIS.
To resolve this issue, change the following Sharepoint registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Intranet\companywe
bpath to match the number listed for the Companyweb Identifier in IIS.
Rerun the CEICW.
or ....
Error 0x80070003 returned from call to Fixing the inheritance for companyweb
dir().
calling Set Web Publishing Rules (0x80070003).
Error 0x80070003 returned from call to CRFireCommit::Commit().
0x80070003 is The system cannot find the path specified.
Is there a companyweb folder under inetpub?
If what you posted earier for web sites in IIS is all you have, you're
missing some items - and it appears that what's there may not be correctly
configured.
It would be really hard to try and fix it piece by piece - without having a
known good configuration to compare it with. The above are examples of
problems that exist, but probably aren't the root cause nor the fix.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"Jake Eyre" <JakeEyre@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D5FD3B8A-7AFD-47D1-B551-77F2E2165EB7@xxxxxxxxxxxxxxxx
Sorry, Les, I'm confused.
What has been massaged to fit with what external DHCP device?
All machines are using the server for DHCP and always have been.
I have no issues with local lan name resolution nor with the DHCP server.
"Les Connor [SBS Community Member - SBS M" wrote:
Not a typo, just explaining that the config *I* posted used that IP.
Jakes is nowhere near standard. Anytime you see an SBS configuration that
has been massaged to fit the DHCP of some external device - flags are
raised.
It might take about forever in a newsgroup setting to accurately discover
the state of this SBS. The guts have been ripped out and replaced, and we
don't know if the plumbing is right ;-).
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"/kj" <kj@xxxxxxxxxxx> wrote in message
news:u7FHMjcKGHA.604@xxxxxxxxxxxxxxxxxxxxxxx
Maybe it was just a type-o?
companyweb 4 Running companyweb 192.168.***<15.2>**** 80 444
/kj
"Jake Eyre" <JakeEyre@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE1D1359-40FF-4287-AB1F-56C1D01BEF82@xxxxxxxxxxxxxxxx
Hi Les,
Not sure where you got the 15.2 from. If you re-read my post, the site
is
on
192.168.0.5
Yes, companyweb has host headers.
The installation history is as follows:
1. Original Install
2. https didn't work straight-away, so I uninstalled and re-installed
IIS;
SharePoint and Exchange.
3. Exchange SP1
4. SBS SP1 5-install set
5. Where we're at now.
Thanks
jake
"Les Connor [SBS Community Member - SBS M" wrote:
Description Identifier State Host header value IP address Port SSL
Port
Status
Default Web Site 1 Running * All Unassigned * 80 443
Microsoft SharePoint Administration 2 Running * All Unassigned *
8883
SharePoint Central Administration 3 Running * All Unassigned * 8081
companyweb 4 Running companyweb 192.168.15.2 80 444
The above is almost default SBS standard - only exception is the
.15.2.
You're missing some stuff, and what you do have doesn't look like
what
SBS
setup would do. What's the installation/modification history here?
No host header for companyweb ?
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and
I'll
understand." - Confucius
"Jake Eyre" <JakeEyre@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:11FA3D96-A466-4D3C-87BD-37E23B38C428@xxxxxxxxxxxxxxxx
Hi Les,
Thanks for the prompt reply.
Default Web Site * All
Unassigned *
80 443
Microsoft SharePoint Administration * All Unassigned * 9192
companyweb 192.168.0.5
80
444
Companyweb doesn't work, now, either. I can get the default website
on
http
internally but not companyweb.
"Les Connor [SBS Community Member - SBS M" wrote:
Hi Jack,
How about having a look in IIS | Web sites - and give us a list of
the
sites
and the ports they're using?
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me
and
I'll
understand." - Confucius
"Jake Eyre" <JakeEyre@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:479245F4-45DA-40DD-B192-B6D4368A713E@xxxxxxxxxxxxxxxx
I am unable to get SSL working on my SBS server. I have run and
re-run
CEICW,
creating a certificate, apparently.
Neither internal nor external clients can connect to 443/https.
I can connect to OWA using http, but only internally, but for
specific
reasons, I cannot forward 80 to the server; it's doing something
else.
In
any
case, I wouldn't really want to open 80 to the server.
If it was just internal who could connect, I would have a
firewall
issue,
or
something along those lines, however, no-one can connect to 443,
not
even
from the server itself. When i check the directory security
settings
after
running CEICW, no SSL is selected, and the original directory
security
IP
setting is there (Only allow local subnet and localhost). If I
manually
tick
the SSL box, I lose access to the http site internally.
I have re-installed both IIS, Exchange and monitoring.
**UPDATE**
TEXT FROM CLEANED ICWLOG.TXT BELOW:
03/02/2006 18:42
C:\Program Files\Microsoft Windows Small Business
Server\Networking\ICW\wizinet.dll, version 5.2.2893.0
calling CNetCommit::ValidatePropertyBag ().
Call to Querying for the property bag () returned ok.
Call to Reading hardware selection () returned ok.
Hardware selection: 0
Call to Validating hardware selection () returned ok.
Call to Reading LAN NIC Guid () returned ok.
LAN NIC Guid: {0C633E42-5829-4508-8662-B5C946E8063E}
Call to Validating LAN NIC Guid () returned ok.
Call to Validating NIC properties () returned ok.
Broadband selection: 1
Call to Validating broadband selection () returned ok.
calling CNetCommit::ValidateRouterConnectionProperties ().
Call to Reading UPNP selection () returned ok.
NOT a UPnP router
Call to Reading Router IP () returned ok.
Router IP: 192.168.0.253
Call to Validating Router IP () returned ok.
Call to Reading preferred DNS server IP () returned ok.
Preferred DNS server IP: 195.26.36.3
Call to Validating preferred DNS server IP () returned ok.
Call to Reading alternate DNS server IP () returned ok.
Alternate DNS server IP: 195.26.37.3
Call to Validating alternate DNS server IP () returned ok.
Call to Validating preferred and alternate DNS servers ()
returned
ok.
Call to Reading router on second NIC () returned ok.
Call to CNetCommit::ValidateRouterConnectionProperties ()
returned
ok.
03/02/2006 18:42
C:\Program Files\Microsoft Windows Small Business
Server\Networking\ICW\wizrfire.dll, version 5.2.2893.0
calling CRFireCommit::ValidatePropertyBag (0x26d198).
Call to This is a Router Single Nic configuration only Web
Publishing
will
be configured, Basic Firewall will not be configured. ()
returned
ok.
Call to Reading web publishing selection () returned ok.
Call to Reading OWA publishing selection () returned ok.
Call to Reading RUP publishing selection () returned ok.
Call to Reading Monitoring publishing selection () returned ok.
Call to Reading OMA publishing selection () returned ok.
Call to Reading RPC publishing selection () returned ok.
Call to Reading Companyweb publishing selection () returned ok.
Call to Reading ROOT publishing selection () returned ok.
Web publishing selections:
OWA publishing: 1
RUP publishing: 1
Monitoring publishing: 1
OMA publishing: 1
RPC publishing: 1
Companyweb publishing: 0
ROOT publishing: 0
Call to CRFireCommit::ValidatePropertyBag () returned ok.
03/02/2006 18:42
C:\Program Files\Microsoft Windows Small Business
Server\Networking\ICW\wizcert.dll, version 5.2.2893.0
Calling CCertCommit::ValidatePropertyBag
Require SSL for OWA: 1
Require SSL for Remote Portal: 1
Require SSL for Monitoring: 0
Require SSL for OMA: 0
Require SSL for CompanyWeb: 0
Require 128 Bit Encryption: 1
Cert selection: 1
Web server name: mx01.wheatsearch.com
CCertCommit::ValidatePropertyBag returned OK
03/02/2006 18:42
C:\Program Files\Microsoft Windows Small Business
Server\Networking\ICW\wizemail.dll, version 5.2.2893.0
calling CEmailCommit::ValidatePropertyBag ().
calling pdispPPPBag->QueryInterface (IPropertyPagePropertyBag,
0x6e50c).
Call to pdispPPPBag->QueryInterface () returned ok.
calling ReadInt4 (0x26d198,
DB5E5E45-3598-4F1D-8FF7-0ED35B9EB6A4).
Call to ReadInt4 () returned ok.
The out param of ReadInt4() is 1.
calling CValidatePropertyUtil.ValidatePropertyInteger ().
Call to CValidatePropertyUtil.ValidatePropertyInteger ()
returned
ok.
calling ReadBool (0x26d198,
F71526DD-9C19-4fe9-B7DB-FD4360909275).
Call to ReadBool () returned ok.
The out param of ReadBool() is 1.
calling CValidatePropertyUtil.ValidatePropertyBool ().
Call to CValidatePropertyUtil.ValidatePropertyBool () returned
ok.
calling ReadBool (0x26d198,
DB5E5E46-3598-4F1D-8FF7-0ED35B9EB6A4).
Call to ReadBool () returned ok.
The out param of ReadBool() is 0.
calling CValidatePropertyUtil.ValidatePropertyBool ().
Call to CValidatePropertyUtil.ValidatePropertyBool () returned
ok.
calling ReadBool (0x26d198,
1DB7A50F-98F8-452f-868B-1AAC56585DD0).
Call to ReadBool () returned ok.
The out param of ReadBool() is 1.
calling CValidatePropertyUtil.ValidatePropertyBool ().
Call to CValidatePropertyUtil.ValidatePropertyBool () returned
ok.
calling ReadInt4 (0x26d198,
C9D8697B-0D4C-4767-8F1F-4CE415098774).
Call to ReadInt4 () returned ok.
The out param of ReadInt4() is 0x2.
calling CValidatePropertyUtil.ValidatePropertyLong ().
Call to CValidatePropertyUtil.ValidatePropertyLong () returned
ok.
calling ReadString (0x26d198,
01637C90-B142-41C4-8520-6B2E0F891BE7).
Call to ReadString () returned ok.
The out param of ReadString() is wheatsearch.com.
calling ReadBool (0x26d198,
1DB7A50F-98F8-452f-868B-1AAC56585DD0).
Call to ReadBool () returned ok.
The out param of ReadBool() is 1.
calling ReadInt4 (0x26d198,
C9D8697B-0D4C-4767-8F1F-4CE415098774).
Call to ReadInt4 () returned ok.
The out param of ReadInt4() is 0x2.
calling CValidatePropertyUtil.ValidatePropertyHostName ().
Call to CValidatePropertyUtil.ValidatePropertyHostName ()
returned
ok.
calling AttachCommiter.Validate(pPPPBag) (0x26d198,
01637C90-B142-41C4-8520-6B2E0F891BE7).
calling CAttachCommiter::Validate (0x26d198).
calling CAttachCommiter::Validate:ReadVariant (0x0).
calling CAttachCommiter::Validate:m_spDoc.CoCreateInstance
(0x0).
calling CAttachCommiter::Validate:m_spDoc->loadXML (0x0).
Call to CAttachCommiter::Validate () returned ok.
Call to CEMailCommit::ValidatePropertyBag () returned ok.
calling CNetCommit::Commit (2544024).
calling CNetCommit::ValidatePropertyBag ().
Call to Querying for the property bag () returned ok.
Property bag is not dirty, skipping validation
calling CNetCommit::Common ().
calling CNetCommit::GetLanNicInfo ().
LAN NIC Guid: {0C633E42-5829-4508-8662-B5C946E8063E}
Call to Converting LAN NIC Guid () returned ok.
Call to Getting IP address for the LAN NIC () returned ok.
Call to Reading in the LAN NIC info () returned ok.
Call to Fixing the TCP/IP NIC Binding order () returned ok.
Dhcp server is installed and not disabled
Call to Set DHCP Server to start up automatically () returned
ok.
DNS server is installed and not disabled
Call to Changing startup type for DNS () returned ok.
Call to Clearing DNS server entries on the LAN NIC () returned
ok.
.
- Follow-Ups:
- Re: Unable to create secure cert for https OWA - Re-submission
- From: Jake Eyre
- Re: Unable to create secure cert for https OWA - Re-submission
- References:
- Unable to create secure cert for https OWA - Re-submission
- From: Jake Eyre
- Re: Unable to create secure cert for https OWA - Re-submission
- From: Les Connor [SBS Community Member - SBS MVP]
- Re: Unable to create secure cert for https OWA - Re-submission
- From: Jake Eyre
- Re: Unable to create secure cert for https OWA - Re-submission
- From: Les Connor [SBS Community Member - SBS MVP]
- Re: Unable to create secure cert for https OWA - Re-submission
- From: Jake Eyre
- Re: Unable to create secure cert for https OWA - Re-submission
- From: /kj
- Re: Unable to create secure cert for https OWA - Re-submission
- From: Les Connor [SBS Community Member - SBS MVP]
- Re: Unable to create secure cert for https OWA - Re-submission
- From: Jake Eyre
- Unable to create secure cert for https OWA - Re-submission
- Prev by Date: Re: OWA not working externally
- Next by Date: Re: Recommendations for good wireless USB/PCI adapters
- Previous by thread: Re: Unable to create secure cert for https OWA - Re-submission
- Next by thread: Re: Unable to create secure cert for https OWA - Re-submission
- Index(es):
Relevant Pages
|