ConnectComputer Mystery

Hi All,

SBS2003 R2 Premium, straight forward new install. Everything is running
fine. No errors on any of the eventlogs. Trying to run connectcomputer we
get a "page cannot be displayed" on http but we can get there with https.
The login window comes up, the users and computers to pick from come up, the
summary page comes up, but when we hit the last button, we are getting an
error message that the installation encountered an error. Below is the link
to join again and we can start all over with the same result.

There are no error messages in the server eventlog. ISA monitoring doesn't
display any error. We checked the virtual directory and it is not set to
require SSL. All NIC cards (except one) are disabled on the client computer
(XP Pro), firewall is disabled and antivirus is uninstalled.

Has anybody seen this before?

Thanks

--
Claus

Hi,

On the client machine , open SBSnetsetup.log in program files\
microsoft windows small business server\clients folder and please
paste it here.

Regards,

Dev
Microsoft EPS SBS Team

Claus wrote:
> Hi All,
>
> SBS2003 R2 Premium, straight forward new install. Everything is running
> fine. No errors on any of the eventlogs. Trying to run connectcomputer we
> get a "page cannot be displayed" on http but we can get there with https.
> The login window comes up, the users and computers to pick from come up, the
> summary page comes up, but when we hit the last button, we are getting an
> error message that the installation encountered an error. Below is the link
> to join again and we can start all over with the same result.
>
> There are no error messages in the server eventlog. ISA monitoring doesn't
> display any error. We checked the virtual directory and it is not set to
> require SSL. All NIC cards (except one) are disabled on the client computer
> (XP Pro), firewall is disabled and antivirus is uninstalled.
>
> Has anybody seen this before?
>
> Thanks
>
> --
> Claus

Hi Dev,

Thanks for answering. Below is the content of the log file. I only pasted
one sequence because they are all identical for each try. I also replaced
the specific info about domain and admin with generic ones. The info in the
log file was correctly showing the right names.

3/24/2007 3:24 PM
-- Starting SBS Net Setup --
found [16] keys
CProfileList::CProfileList() - added [1006, C:\Documents and Settings\admin]
to the profile dir map
CProfileList::CProfileList() - added [500, C:\Documents and
Settings\Administrator] to the profile dir map
CProfileList::CProfileList() - added [admin, C:\Documents and
Settings\admin] to the profile dir map
CProfileList::CProfileList() - added [Administrator, C:\Documents and
Settings\Administrator] to the profile dir map
CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: kennlawkeeper
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://Servername.Domain.local/DC=Domain,DC=local, administrator, [PW] )
CAuthPage::GetUsersAndComputers() - ADsOpenObject(
LDAP://Servername.Domain.local/DC=Domain,DC=local, administrator, [PW] )
CAuthPage::OnNotify() - PSN_SETACTIVE - our computer name IS in the AD
OpenXMLFile() - DOMDocument::load( C:\Program Files\Microsoft Windows Small
Business Server\Clients\usermap.txt ) failed - [1]
CWizard::PrepAutoLogon()
CWizard::PrepAutoLogon() - runonce key set
CWizard::PrepAutoLogon() - account existed, deleting
CWizard::PrepAutoLogon() - setting DefaultDomainName_PostMigrate to
[Domain], [0]
FinishNetworkingSetup()
CWizard::FinishNetworkingSetup() - outputting XML file
FinishNetworkingSetup() -- calling NetJoinDomain( NULL, kennlaw.local,
ou=sbscomputers,ou=computers,ou=mybusiness,dc=Domain,dc=local,
Domain.local\administrator, [pw], 359 )
FinishNetworkingSetup() -- NetJoinDomain() failed [1727], returning
FinishNetworkingSetup() failed -- hr == [-2147467259]
Deleted sbsmig out of runonce key.
--
Claus
"DEV" <devrawat2@gmail.com> wrote in message
news:1174856926.246539.267900@b75g2000hsg.googlegroups.com...
> Hi,
>
> On the client machine , open SBSnetsetup.log in program files\
> microsoft windows small business server\clients folder and please
> paste it here.
>
> Regards,
>
> Dev
> Microsoft EPS SBS Team
>
> Claus wrote:
>> Hi All,
>>
>> SBS2003 R2 Premium, straight forward new install. Everything is running
>> fine. No errors on any of the eventlogs. Trying to run connectcomputer we
>> get a "page cannot be displayed" on http but we can get there with https.
>> The login window comes up, the users and computers to pick from come up,
>> the
>> summary page comes up, but when we hit the last button, we are getting an
>> error message that the installation encountered an error. Below is the
>> link
>> to join again and we can start all over with the same result.
>>
>> There are no error messages in the server eventlog. ISA monitoring
>> doesn't
>> display any error. We checked the virtual directory and it is not set to
>> require SSL. All NIC cards (except one) are disabled on the client
>> computer
>> (XP Pro), firewall is disabled and antivirus is uninstalled.
>>
>> Has anybody seen this before?
>>
>> Thanks
>>
>> --
>> Claus
>

Hi Claus,

Thanks for posting here.

According to your description, I understand that you cannot join the new
client computer into SBS 2003 Domain by using
http://SBSServerName/connectcomputer link. If I have misunderstood the
problem, please don't hesitate to let me know.

I.To narrow down this issue, please kindly answer and perform the following
questions and steps:

1.Regarding the SMB, you could use the following steps to disable it on the
SBS server.

A. On the SBS server, run "gpmc.msc" and make sure the following policies
(10 in total) are all ''Disable'' (instead of ''Not defined'') in BOTH
''Default Domain Security Policy'' and ''Default Domain Controller Security
Policy'':

NOTE: The polices are under ''Windows Settings'' -> ''Security Settings''
-> ''Local Policies'' -> ''Security Options''.

1) Microsoft network client: Digitally sign communications (always):
Disabled
2) Microsoft network client: Digitally sign communications (if server
agrees): Disabled
3) Microsoft network server: Digitally sign communications (always):
Disabled
4) Microsoft network server: Digitally sign communications (if client
agrees): Disabled
5) Network security: LAN Manager authentication level: Send LM & NTLM - use
NTLMv2 session security if negotiated

B. Restart the DC and client computer to take effect.

C. On the client computer, make sure the value of the following keys are
all ''0'':

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
\enablesecuritysignature
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
\requiresecuritysignature
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
eters\enablesecuritysignature
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
eters\requiresecuritysignature

2. What's the exact error message when you try to join the new client
computer into SBS 2003 Domain by using http://SBSServerName/connectcomputer
link? Please kindly send me the screen shot of the error message as an
email attachment.

To do this, please follow the steps below:

a) When the screen appears, press PrScrn (this key is located to the right
of the
F12 key on the keyboard)
b) Create a new Word document and open it.
c) Press Ctrl + V to paste the screen shot into the document.
d) Send this document as the mail's attachment to my mailbox:
v-jaluo@microsoft.com

3.On the SBS Server, can you access this webpage by using
http://localhost/connectcomputer or http://SBSServerName/connectcomputer
link?

4.Have you run the CEICW? Please re-run the CEICW, go through all the steps
in the wizard to configure your SBS network and IIS as well. Reference:

825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763

5.Please run "ipconfig /all" (without the quotation marks) on the command
prompt on the specific problematic client computer and a working client
workstation, and then compare the output to verify the configuration of
TCP/IP on the specific problematic client computer.

6.Meanwhile, you may try the following steps on the client workstation and
see how it goes:

a. Log on locally as a local administrator to the client. In Control Panel,
double-click System. On the Computer Name tab, click Change, select
Workgroup, type a workgroup name and click OK. Click OK when prompted to
restart the computer.

b. On the SBS server, delete the user and computer accounts, click Add a
User in Server Management\Users. Follow the instructions to create user and
computer accounts.

c. On the client, open IE, go to http://SBSServerName/connectcomputer and
follow the instructions to join domain.

7.If the issue persists, you may try the steps below to manually join
domain:

a. Log on local as a local administrator to the client, add the domain user
to the local Administrators group.

b. In Control Panel, double-click System. On the Computer Name tab, click
Change, select Domain, type your domain name and click OK. You'll be
prompted to enter the domain admin's credential. Enter the credential,
click OK, wait a while and you'll see a dialog box with the message
"Welcome to the xxx domain". Restart the computer as prompted.

c. Log on as the domain user.

8.make sure to enable anonymous access and do not require SSL on the
ConnectComputer virtual directory.
to do so:
A. Go to IIS and expand servername -> Web Sites -> Default Web Site.
B. right click ConnectComputer,go to directory security tab.
C. in the authentication and access control panel,click edit,check "enable
anonymous access",uncheck integrated windows authentication.click OK.
D. in the secure communications panel,click edit,uncheck "require secure
channel(SSL)",click OK.

9.Reinstall ConnectComputer and see if it helps:

A. Go to IIS and expand servername -> Web Sites -> Default Web Site. Delete
the ConnectComputer vdir.
B. Rename the C:\Inetpub\ConnectComputer folder.
C. Create new folder named ConnectComputer under C:\Inetpub.
D. Copy all the files from the SBS2K3 media
cd3:\SBS\ClientSetup\ClientSetup to the C:\Inetpub\ConnectComputer
directory. Make sure to remove the "Read-only" attributes from the files.
E. Right-click on Default Web Site in IIS, choose New -> Virtual Directory.
F. In the Alias field, type in ConnectComputer and click Next.
G. In the path box, browse to C:\Inetpub\ConnectComputer.
H. Click Next through the wizard, the default permissions are the default
for ConnectComputer.
I. Once it is completed, right-click on ConnectComptuer and select
Properties.
J. Click Remove for the "Application name" under the "Application settings"
at the bottom of the Virtual Directory tab.
K. Click on the Directory Security tab, click Edit for "Authentication and
access control".
L. Uncheck "Integrated Windows authentication", click OK.
M. Click on the Edit button on the "IP address and domain name
restrictions".
N. Put the bullet next to "Denied access" and then click Add.
O. Add 127.0.0.1 and the internal subnet (192.168.16.2/255.255.255.0 is the
default). Click OK.
P. Click OK out of the ConnectComputer properties.


II.If the issue persists, please kindly help me collect the following
information for further analysis:

1.Please run "ipconfig /all >c:\ipconfig.txt" (Without the quotation marks)
on the command prompt on the SBS Server and the specific workstation, and
then send these files to me.

2.can you access owa and RWW by http://servername/exchange and
http://servername/remote

3.Send SBSNetSetup.log from C:\Program Files\Microsoft Windows Small
Business Server\Clients at the problematic client workstation to me

4.Send NetSetup.log from %windir%\debug at the problematic client
workstation to me.

5.Gather IIS Metabase from SBS Server
===========================
a. Install .NET Framework Version 1.1:
http://www.microsoft.com/downloads/d...5e3-f589-4842-
8157-034d1e7cf3a3&DisplayLang=en.
b. Install MBExplorer by installing IIS 6 Resource Kit Tools:
http://www.microsoft.com/downloads/d...2EE-A71A-4C73-
B628-ADE629C89499&displaylang=en.
c. Once it is installed, access it from Start, Programs, IIS Resources,
Metabase Explorer.
d. In the left pane, right click ''LM'' (under your server computer name)
to choose ''Export to file'', and then save it as IIS.mbk.
e. Compress this mbk file and send it to me for analysis.

6.IIS logs
========
a. Open IIS.
b. Locate Default web site. Right-click it and then click Properties.
c. Click to selected Enable logging and then click properties.
d. Click Advanced.
e. Click to select every checkbox here.
f. Click OK to close these windows.
g. Reproduce this issue and send the logs to me.

NOTE: The log files are located at %systemroot%\System32\LogFiles by
default.

Please compress all the files and send to me at v-jaluo@microsoft.com

I appreciate your time and cooperation. Please do not hesitate to let me
know if you have any further concerns, I am looking forward to hearing from
you.

Have a nice day!

Best regards,

Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================

Hi Jacky,

Thanks for your response. Some of your questions had been answered in the
original email. For several other issues that indicate an "upnormal" SBS
installation, we decided to wipe the server and start from scratch. I will
use your suggestions below for future troubleshooting. If we run into the
same issue again after rebuilt, I will post back here.

--
Claus
""Jacky Luo [MSFT]"" <v-jaluo@online.microsoft.com> wrote in message
news:DnrNyo6bHHA.1820@TK2MSFTNGHUB02.phx.gbl...
> Hi Claus,
>
> Thanks for posting here.
>
> According to your description, I understand that you cannot join the new
> client computer into SBS 2003 Domain by using
> http://SBSServerName/connectcomputer link. If I have misunderstood the
> problem, please don't hesitate to let me know.
>
> I.To narrow down this issue, please kindly answer and perform the
> following
> questions and steps:
>
> 1.Regarding the SMB, you could use the following steps to disable it on
> the
> SBS server.
>
> A. On the SBS server, run "gpmc.msc" and make sure the following policies
> (10 in total) are all ''Disable'' (instead of ''Not defined'') in BOTH
> ''Default Domain Security Policy'' and ''Default Domain Controller
> Security
> Policy'':
>
> NOTE: The polices are under ''Windows Settings'' -> ''Security Settings''
> -> ''Local Policies'' -> ''Security Options''.
>
> 1) Microsoft network client: Digitally sign communications (always):
> Disabled
> 2) Microsoft network client: Digitally sign communications (if server
> agrees): Disabled
> 3) Microsoft network server: Digitally sign communications (always):
> Disabled
> 4) Microsoft network server: Digitally sign communications (if client
> agrees): Disabled
> 5) Network security: LAN Manager authentication level: Send LM & NTLM -
> use
> NTLMv2 session security if negotiated
>
> B. Restart the DC and client computer to take effect.
>
> C. On the client computer, make sure the value of the following keys are
> all ''0'':
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
> \enablesecuritysignature
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
> \requiresecuritysignature
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
> eters\enablesecuritysignature
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
> eters\requiresecuritysignature
>
> 2. What's the exact error message when you try to join the new client
> computer into SBS 2003 Domain by using
> http://SBSServerName/connectcomputer
> link? Please kindly send me the screen shot of the error message as an
> email attachment.
>
> To do this, please follow the steps below:
>
> a) When the screen appears, press PrScrn (this key is located to the right
> of the
> F12 key on the keyboard)
> b) Create a new Word document and open it.
> c) Press Ctrl + V to paste the screen shot into the document.
> d) Send this document as the mail's attachment to my mailbox:
> v-jaluo@microsoft.com
>
> 3.On the SBS Server, can you access this webpage by using
> http://localhost/connectcomputer or http://SBSServerName/connectcomputer
> link?
>
> 4.Have you run the CEICW? Please re-run the CEICW, go through all the
> steps
> in the wizard to configure your SBS network and IIS as well. Reference:
>
> 825763 How to configure Internet access in Windows Small Business Server
> 2003
> http://support.microsoft.com/?id=825763
>
> 5.Please run "ipconfig /all" (without the quotation marks) on the command
> prompt on the specific problematic client computer and a working client
> workstation, and then compare the output to verify the configuration of
> TCP/IP on the specific problematic client computer.
>
> 6.Meanwhile, you may try the following steps on the client workstation and
> see how it goes:
>
> a. Log on locally as a local administrator to the client. In Control
> Panel,
> double-click System. On the Computer Name tab, click Change, select
> Workgroup, type a workgroup name and click OK. Click OK when prompted to
> restart the computer.
>
> b. On the SBS server, delete the user and computer accounts, click Add a
> User in Server Management\Users. Follow the instructions to create user
> and
> computer accounts.
>
> c. On the client, open IE, go to http://SBSServerName/connectcomputer and
> follow the instructions to join domain.
>
> 7.If the issue persists, you may try the steps below to manually join
> domain:
>
> a. Log on local as a local administrator to the client, add the domain
> user
> to the local Administrators group.
>
> b. In Control Panel, double-click System. On the Computer Name tab, click
> Change, select Domain, type your domain name and click OK. You'll be
> prompted to enter the domain admin's credential. Enter the credential,
> click OK, wait a while and you'll see a dialog box with the message
> "Welcome to the xxx domain". Restart the computer as prompted.
>
> c. Log on as the domain user.
>
> 8.make sure to enable anonymous access and do not require SSL on the
> ConnectComputer virtual directory.
> to do so:
> A. Go to IIS and expand servername -> Web Sites -> Default Web Site.
> B. right click ConnectComputer,go to directory security tab.
> C. in the authentication and access control panel,click edit,check "enable
> anonymous access",uncheck integrated windows authentication.click OK.
> D. in the secure communications panel,click edit,uncheck "require secure
> channel(SSL)",click OK.
>
> 9.Reinstall ConnectComputer and see if it helps:
>
> A. Go to IIS and expand servername -> Web Sites -> Default Web Site.
> Delete
> the ConnectComputer vdir.
> B. Rename the C:\Inetpub\ConnectComputer folder.
> C. Create new folder named ConnectComputer under C:\Inetpub.
> D. Copy all the files from the SBS2K3 media
> cd3:\SBS\ClientSetup\ClientSetup to the C:\Inetpub\ConnectComputer
> directory. Make sure to remove the "Read-only" attributes from the files.
> E. Right-click on Default Web Site in IIS, choose New -> Virtual
> Directory.
> F. In the Alias field, type in ConnectComputer and click Next.
> G. In the path box, browse to C:\Inetpub\ConnectComputer.
> H. Click Next through the wizard, the default permissions are the default
> for ConnectComputer.
> I. Once it is completed, right-click on ConnectComptuer and select
> Properties.
> J. Click Remove for the "Application name" under the "Application
> settings"
> at the bottom of the Virtual Directory tab.
> K. Click on the Directory Security tab, click Edit for "Authentication and
> access control".
> L. Uncheck "Integrated Windows authentication", click OK.
> M. Click on the Edit button on the "IP address and domain name
> restrictions".
> N. Put the bullet next to "Denied access" and then click Add.
> O. Add 127.0.0.1 and the internal subnet (192.168.16.2/255.255.255.0 is
> the
> default). Click OK.
> P. Click OK out of the ConnectComputer properties.
>
>
> II.If the issue persists, please kindly help me collect the following
> information for further analysis:
>
> 1.Please run "ipconfig /all >c:\ipconfig.txt" (Without the quotation
> marks)
> on the command prompt on the SBS Server and the specific workstation, and
> then send these files to me.
>
> 2.can you access owa and RWW by http://servername/exchange and
> http://servername/remote
>
> 3.Send SBSNetSetup.log from C:\Program Files\Microsoft Windows Small
> Business Server\Clients at the problematic client workstation to me
>
> 4.Send NetSetup.log from %windir%\debug at the problematic client
> workstation to me.
>
> 5.Gather IIS Metabase from SBS Server
> ===========================
> a. Install .NET Framework Version 1.1:
> http://www.microsoft.com/downloads/d...5e3-f589-4842-
> 8157-034d1e7cf3a3&DisplayLang=en.
> b. Install MBExplorer by installing IIS 6 Resource Kit Tools:
> http://www.microsoft.com/downloads/d...2EE-A71A-4C73-
> B628-ADE629C89499&displaylang=en.
> c. Once it is installed, access it from Start, Programs, IIS Resources,
> Metabase Explorer.
> d. In the left pane, right click ''LM'' (under your server computer name)
> to choose ''Export to file'', and then save it as IIS.mbk.
> e. Compress this mbk file and send it to me for analysis.
>
> 6.IIS logs
> ========
> a. Open IIS.
> b. Locate Default web site. Right-click it and then click Properties.
> c. Click to selected Enable logging and then click properties.
> d. Click Advanced.
> e. Click to select every checkbox here.
> f. Click OK to close these windows.
> g. Reproduce this issue and send the logs to me.
>
> NOTE: The log files are located at %systemroot%\System32\LogFiles by
> default.
>
> Please compress all the files and send to me at v-jaluo@microsoft.com
>
> I appreciate your time and cooperation. Please do not hesitate to let me
> know if you have any further concerns, I am looking forward to hearing
> from
> you.
>
> Have a nice day!
>
> Best regards,
>
> Jacky Luo (MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ====================================================
> PLEASE NOTE: The partner managed newsgroups are provided to
> assist with break/fix issues and simple how to questions.
> We also love to hear your product feedback! Let us know what you think by
> posting
>
> from the web interface: Partner Feedback
> from your newsreader: microsoft.private.directaccess.partnerfeedback.
>
> We look forward to hearing from you!
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader
> so that others may learn and benefit from this issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ====================================================
>
>
>
>

Hi Claus..

Its a simple DNS issue. have you rebuilt the server already ??

Regards,

Dev
Microsoft EPS SBS Team

Claus wrote:
> Hi Jacky,
>
> Thanks for your response. Some of your questions had been answered in the
> original email. For several other issues that indicate an "upnormal" SBS
> installation, we decided to wipe the server and start from scratch. I will
> use your suggestions below for future troubleshooting. If we run into the
> same issue again after rebuilt, I will post back here.
>
> --
> Claus
> ""Jacky Luo [MSFT]"" <v-jaluo@online.microsoft.com> wrote in message
> news:DnrNyo6bHHA.1820@TK2MSFTNGHUB02.phx.gbl...
> > Hi Claus,
> >
> > Thanks for posting here.
> >
> > According to your description, I understand that you cannot join the new
> > client computer into SBS 2003 Domain by using
> > http://SBSServerName/connectcomputer link. If I have misunderstood the
> > problem, please don't hesitate to let me know.
> >
> > I.To narrow down this issue, please kindly answer and perform the
> > following
> > questions and steps:
> >
> > 1.Regarding the SMB, you could use the following steps to disable it on
> > the
> > SBS server.
> >
> > A. On the SBS server, run "gpmc.msc" and make sure the following policies
> > (10 in total) are all ''Disable'' (instead of ''Not defined'') in BOTH
> > ''Default Domain Security Policy'' and ''Default Domain Controller
> > Security
> > Policy'':
> >
> > NOTE: The polices are under ''Windows Settings'' -> ''Security Settings''
> > -> ''Local Policies'' -> ''Security Options''.
> >
> > 1) Microsoft network client: Digitally sign communications (always):
> > Disabled
> > 2) Microsoft network client: Digitally sign communications (if server
> > agrees): Disabled
> > 3) Microsoft network server: Digitally sign communications (always):
> > Disabled
> > 4) Microsoft network server: Digitally sign communications (if client
> > agrees): Disabled
> > 5) Network security: LAN Manager authentication level: Send LM & NTLM -
> > use
> > NTLMv2 session security if negotiated
> >
> > B. Restart the DC and client computer to take effect.
> >
> > C. On the client computer, make sure the value of the following keys are
> > all ''0'':
> >
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
> > \enablesecuritysignature
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
> > \requiresecuritysignature
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
> > eters\enablesecuritysignature
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
> > eters\requiresecuritysignature
> >
> > 2. What's the exact error message when you try to join the new client
> > computer into SBS 2003 Domain by using
> > http://SBSServerName/connectcomputer
> > link? Please kindly send me the screen shot of the error message as an
> > email attachment.
> >
> > To do this, please follow the steps below:
> >
> > a) When the screen appears, press PrScrn (this key is located to the right
> > of the
> > F12 key on the keyboard)
> > b) Create a new Word document and open it.
> > c) Press Ctrl + V to paste the screen shot into the document.
> > d) Send this document as the mail's attachment to my mailbox:
> > v-jaluo@microsoft.com
> >
> > 3.On the SBS Server, can you access this webpage by using
> > http://localhost/connectcomputer or http://SBSServerName/connectcomputer
> > link?
> >
> > 4.Have you run the CEICW? Please re-run the CEICW, go through all the
> > steps
> > in the wizard to configure your SBS network and IIS as well. Reference:
> >
> > 825763 How to configure Internet access in Windows Small Business Server
> > 2003
> > http://support.microsoft.com/?id=825763
> >
> > 5.Please run "ipconfig /all" (without the quotation marks) on the command
> > prompt on the specific problematic client computer and a working client
> > workstation, and then compare the output to verify the configuration of
> > TCP/IP on the specific problematic client computer.
> >
> > 6.Meanwhile, you may try the following steps on the client workstation and
> > see how it goes:
> >
> > a. Log on locally as a local administrator to the client. In Control
> > Panel,
> > double-click System. On the Computer Name tab, click Change, select
> > Workgroup, type a workgroup name and click OK. Click OK when prompted to
> > restart the computer.
> >
> > b. On the SBS server, delete the user and computer accounts, click Add a
> > User in Server Management\Users. Follow the instructions to create user
> > and
> > computer accounts.
> >
> > c. On the client, open IE, go to http://SBSServerName/connectcomputer and
> > follow the instructions to join domain.
> >
> > 7.If the issue persists, you may try the steps below to manually join
> > domain:
> >
> > a. Log on local as a local administrator to the client, add the domain
> > user
> > to the local Administrators group.
> >
> > b. In Control Panel, double-click System. On the Computer Name tab, click
> > Change, select Domain, type your domain name and click OK. You'll be
> > prompted to enter the domain admin's credential. Enter the credential,
> > click OK, wait a while and you'll see a dialog box with the message
> > "Welcome to the xxx domain". Restart the computer as prompted.
> >
> > c. Log on as the domain user.
> >
> > 8.make sure to enable anonymous access and do not require SSL on the
> > ConnectComputer virtual directory.
> > to do so:
> > A. Go to IIS and expand servername -> Web Sites -> Default Web Site.
> > B. right click ConnectComputer,go to directory security tab.
> > C. in the authentication and access control panel,click edit,check "enable
> > anonymous access",uncheck integrated windows authentication.click OK.
> > D. in the secure communications panel,click edit,uncheck "require secure
> > channel(SSL)",click OK.
> >
> > 9.Reinstall ConnectComputer and see if it helps:
> >
> > A. Go to IIS and expand servername -> Web Sites -> Default Web Site.
> > Delete
> > the ConnectComputer vdir.
> > B. Rename the C:\Inetpub\ConnectComputer folder.
> > C. Create new folder named ConnectComputer under C:\Inetpub.
> > D. Copy all the files from the SBS2K3 media
> > cd3:\SBS\ClientSetup\ClientSetup to the C:\Inetpub\ConnectComputer
> > directory. Make sure to remove the "Read-only" attributes from the files.
> > E. Right-click on Default Web Site in IIS, choose New -> Virtual
> > Directory.
> > F. In the Alias field, type in ConnectComputer and click Next.
> > G. In the path box, browse to C:\Inetpub\ConnectComputer.
> > H. Click Next through the wizard, the default permissions are the default
> > for ConnectComputer.
> > I. Once it is completed, right-click on ConnectComptuer and select
> > Properties.
> > J. Click Remove for the "Application name" under the "Application
> > settings"
> > at the bottom of the Virtual Directory tab.
> > K. Click on the Directory Security tab, click Edit for "Authentication and
> > access control".
> > L. Uncheck "Integrated Windows authentication", click OK.
> > M. Click on the Edit button on the "IP address and domain name
> > restrictions".
> > N. Put the bullet next to "Denied access" and then click Add.
> > O. Add 127.0.0.1 and the internal subnet (192.168.16.2/255.255.255.0 is
> > the
> > default). Click OK.
> > P. Click OK out of the ConnectComputer properties.
> >
> >
> > II.If the issue persists, please kindly help me collect the following
> > information for further analysis:
> >
> > 1.Please run "ipconfig /all >c:\ipconfig.txt" (Without the quotation
> > marks)
> > on the command prompt on the SBS Server and the specific workstation, and
> > then send these files to me.
> >
> > 2.can you access owa and RWW by http://servername/exchange and
> > http://servername/remote
> >
> > 3.Send SBSNetSetup.log from C:\Program Files\Microsoft Windows Small
> > Business Server\Clients at the problematic client workstation to me
> >
> > 4.Send NetSetup.log from %windir%\debug at the problematic client
> > workstation to me.
> >
> > 5.Gather IIS Metabase from SBS Server
> > ===========================
> > a. Install .NET Framework Version 1.1:
> > http://www.microsoft.com/downloads/d...5e3-f589-4842-
> > 8157-034d1e7cf3a3&DisplayLang=en.
> > b. Install MBExplorer by installing IIS 6 Resource Kit Tools:
> > http://www.microsoft.com/downloads/d...2EE-A71A-4C73-
> > B628-ADE629C89499&displaylang=en.
> > c. Once it is installed, access it from Start, Programs, IIS Resources,
> > Metabase Explorer.
> > d. In the left pane, right click ''LM'' (under your server computer name)
> > to choose ''Export to file'', and then save it as IIS.mbk.
> > e. Compress this mbk file and send it to me for analysis.
> >
> > 6.IIS logs
> > ========
> > a. Open IIS.
> > b. Locate Default web site. Right-click it and then click Properties.
> > c. Click to selected Enable logging and then click properties.
> > d. Click Advanced.
> > e. Click to select every checkbox here.
> > f. Click OK to close these windows.
> > g. Reproduce this issue and send the logs to me.
> >
> > NOTE: The log files are located at %systemroot%\System32\LogFiles by
> > default.
> >
> > Please compress all the files and send to me at v-jaluo@microsoft.com
> >
> > I appreciate your time and cooperation. Please do not hesitate to let me
> > know if you have any further concerns, I am looking forward to hearing
> > from
> > you.
> >
> > Have a nice day!
> >
> > Best regards,
> >
> > Jacky Luo (MSFT)
> > Microsoft CSS Online Newsgroup Support
> >
> > Get Secure! - www.microsoft.com/security
> > ====================================================
> > PLEASE NOTE: The partner managed newsgroups are provided to
> > assist with break/fix issues and simple how to questions.
> > We also love to hear your product feedback! Let us know what you think by
> > posting
> >
> > from the web interface: Partner Feedback
> > from your newsreader: microsoft.private.directaccess.partnerfeedback.
> >
> > We look forward to hearing from you!
> > ====================================================
> > When responding to posts, please "Reply to Group" via your newsreader
> > so that others may learn and benefit from this issue.
> > ====================================================
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > ====================================================
> >
> >
> >
> >

Hi Claus,

Thanks for posting back.


you may feel free to post back when you have any update and we will be here
for you.

have a great day!


Best regards,

Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================

Yes, for other reasons. But please tell me what you think so I can
troubleshoot this next time.

--
Claus
"DEV" <devrawat2@gmail.com> wrote in message
news:1174952289.677697.116020@p77g2000hsh.googlegroups.com...
> Hi Claus..
>
> Its a simple DNS issue. have you rebuilt the server already ??
>
> Regards,
>
> Dev
> Microsoft EPS SBS Team
>
> Claus wrote:
>> Hi Jacky,
>>
>> Thanks for your response. Some of your questions had been answered in the
>> original email. For several other issues that indicate an "upnormal" SBS
>> installation, we decided to wipe the server and start from scratch. I
>> will
>> use your suggestions below for future troubleshooting. If we run into the
>> same issue again after rebuilt, I will post back here.
>>
>> --
>> Claus
>> ""Jacky Luo [MSFT]"" <v-jaluo@online.microsoft.com> wrote in message
>> news:DnrNyo6bHHA.1820@TK2MSFTNGHUB02.phx.gbl...
>> > Hi Claus,
>> >
>> > Thanks for posting here.
>> >
>> > According to your description, I understand that you cannot join the
>> > new
>> > client computer into SBS 2003 Domain by using
>> > http://SBSServerName/connectcomputer link. If I have misunderstood the
>> > problem, please don't hesitate to let me know.
>> >
>> > I.To narrow down this issue, please kindly answer and perform the
>> > following
>> > questions and steps:
>> >
>> > 1.Regarding the SMB, you could use the following steps to disable it on
>> > the
>> > SBS server.
>> >
>> > A. On the SBS server, run "gpmc.msc" and make sure the following
>> > policies
>> > (10 in total) are all ''Disable'' (instead of ''Not defined'') in BOTH
>> > ''Default Domain Security Policy'' and ''Default Domain Controller
>> > Security
>> > Policy'':
>> >
>> > NOTE: The polices are under ''Windows Settings'' -> ''Security
>> > Settings''
>> > -> ''Local Policies'' -> ''Security Options''.
>> >
>> > 1) Microsoft network client: Digitally sign communications (always):
>> > Disabled
>> > 2) Microsoft network client: Digitally sign communications (if server
>> > agrees): Disabled
>> > 3) Microsoft network server: Digitally sign communications (always):
>> > Disabled
>> > 4) Microsoft network server: Digitally sign communications (if client
>> > agrees): Disabled
>> > 5) Network security: LAN Manager authentication level: Send LM & NTLM -
>> > use
>> > NTLMv2 session security if negotiated
>> >
>> > B. Restart the DC and client computer to take effect.
>> >
>> > C. On the client computer, make sure the value of the following keys
>> > are
>> > all ''0'':
>> >
>> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
>> > \enablesecuritysignature
>> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
>> > \requiresecuritysignature
>> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
>> > eters\enablesecuritysignature
>> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\param
>> > eters\requiresecuritysignature
>> >
>> > 2. What's the exact error message when you try to join the new client
>> > computer into SBS 2003 Domain by using
>> > http://SBSServerName/connectcomputer
>> > link? Please kindly send me the screen shot of the error message as an
>> > email attachment.
>> >
>> > To do this, please follow the steps below:
>> >
>> > a) When the screen appears, press PrScrn (this key is located to the
>> > right
>> > of the
>> > F12 key on the keyboard)
>> > b) Create a new Word document and open it.
>> > c) Press Ctrl + V to paste the screen shot into the document.
>> > d) Send this document as the mail's attachment to my mailbox:
>> > v-jaluo@microsoft.com
>> >
>> > 3.On the SBS Server, can you access this webpage by using
>> > http://localhost/connectcomputer or
>> > http://SBSServerName/connectcomputer
>> > link?
>> >
>> > 4.Have you run the CEICW? Please re-run the CEICW, go through all the
>> > steps
>> > in the wizard to configure your SBS network and IIS as well. Reference:
>> >
>> > 825763 How to configure Internet access in Windows Small Business
>> > Server
>> > 2003
>> > http://support.microsoft.com/?id=825763
>> >
>> > 5.Please run "ipconfig /all" (without the quotation marks) on the
>> > command
>> > prompt on the specific problematic client computer and a working client
>> > workstation, and then compare the output to verify the configuration of
>> > TCP/IP on the specific problematic client computer.
>> >
>> > 6.Meanwhile, you may try the following steps on the client workstation
>> > and
>> > see how it goes:
>> >
>> > a. Log on locally as a local administrator to the client. In Control
>> > Panel,
>> > double-click System. On the Computer Name tab, click Change, select
>> > Workgroup, type a workgroup name and click OK. Click OK when prompted
>> > to
>> > restart the computer.
>> >
>> > b. On the SBS server, delete the user and computer accounts, click Add
>> > a
>> > User in Server Management\Users. Follow the instructions to create user
>> > and
>> > computer accounts.
>> >
>> > c. On the client, open IE, go to http://SBSServerName/connectcomputer
>> > and
>> > follow the instructions to join domain.
>> >
>> > 7.If the issue persists, you may try the steps below to manually join
>> > domain:
>> >
>> > a. Log on local as a local administrator to the client, add the domain
>> > user
>> > to the local Administrators group.
>> >
>> > b. In Control Panel, double-click System. On the Computer Name tab,
>> > click
>> > Change, select Domain, type your domain name and click OK. You'll be
>> > prompted to enter the domain admin's credential. Enter the credential,
>> > click OK, wait a while and you'll see a dialog box with the message
>> > "Welcome to the xxx domain". Restart the computer as prompted.
>> >
>> > c. Log on as the domain user.
>> >
>> > 8.make sure to enable anonymous access and do not require SSL on the
>> > ConnectComputer virtual directory.
>> > to do so:
>> > A. Go to IIS and expand servername -> Web Sites -> Default Web Site.
>> > B. right click ConnectComputer,go to directory security tab.
>> > C. in the authentication and access control panel,click edit,check
>> > "enable
>> > anonymous access",uncheck integrated windows authentication.click OK.
>> > D. in the secure communications panel,click edit,uncheck "require
>> > secure
>> > channel(SSL)",click OK.
>> >
>> > 9.Reinstall ConnectComputer and see if it helps:
>> >
>> > A. Go to IIS and expand servername -> Web Sites -> Default Web Site.
>> > Delete
>> > the ConnectComputer vdir.
>> > B. Rename the C:\Inetpub\ConnectComputer folder.
>> > C. Create new folder named ConnectComputer under C:\Inetpub.
>> > D. Copy all the files from the SBS2K3 media
>> > cd3:\SBS\ClientSetup\ClientSetup to the C:\Inetpub\ConnectComputer
>> > directory. Make sure to remove the "Read-only" attributes from the
>> > files.
>> > E. Right-click on Default Web Site in IIS, choose New -> Virtual
>> > Directory.
>> > F. In the Alias field, type in ConnectComputer and click Next.
>> > G. In the path box, browse to C:\Inetpub\ConnectComputer.
>> > H. Click Next through the wizard, the default permissions are the
>> > default
>> > for ConnectComputer.
>> > I. Once it is completed, right-click on ConnectComptuer and select
>> > Properties.
>> > J. Click Remove for the "Application name" under the "Application
>> > settings"
>> > at the bottom of the Virtual Directory tab.
>> > K. Click on the Directory Security tab, click Edit for "Authentication
>> > and
>> > access control".
>> > L. Uncheck "Integrated Windows authentication", click OK.
>> > M. Click on the Edit button on the "IP address and domain name
>> > restrictions".
>> > N. Put the bullet next to "Denied access" and then click Add.
>> > O. Add 127.0.0.1 and the internal subnet (192.168.16.2/255.255.255.0 is
>> > the
>> > default). Click OK.
>> > P. Click OK out of the ConnectComputer properties.
>> >
>> >
>> > II.If the issue persists, please kindly help me collect the following
>> > information for further analysis:
>> >
>> > 1.Please run "ipconfig /all >c:\ipconfig.txt" (Without the quotation
>> > marks)
>> > on the command prompt on the SBS Server and the specific workstation,
>> > and
>> > then send these files to me.
>> >
>> > 2.can you access owa and RWW by http://servername/exchange and
>> > http://servername/remote
>> >
>> > 3.Send SBSNetSetup.log from C:\Program Files\Microsoft Windows Small
>> > Business Server\Clients at the problematic client workstation to me
>> >
>> > 4.Send NetSetup.log from %windir%\debug at the problematic client
>> > workstation to me.
>> >
>> > 5.Gather IIS Metabase from SBS Server
>> > ===========================
>> > a. Install .NET Framework Version 1.1:
>> > http://www.microsoft.com/downloads/d...5e3-f589-4842-
>> > 8157-034d1e7cf3a3&DisplayLang=en.
>> > b. Install MBExplorer by installing IIS 6 Resource Kit Tools:
>> > http://www.microsoft.com/downloads/d...2EE-A71A-4C73-
>> > B628-ADE629C89499&displaylang=en.
>> > c. Once it is installed, access it from Start, Programs, IIS Resources,
>> > Metabase Explorer.
>> > d. In the left pane, right click ''LM'' (under your server computer
>> > name)
>> > to choose ''Export to file'', and then save it as IIS.mbk.
>> > e. Compress this mbk file and send it to me for analysis.
>> >
>> > 6.IIS logs
>> > ========
>> > a. Open IIS.
>> > b. Locate Default web site. Right-click it and then click Properties.
>> > c. Click to selected Enable logging and then click properties.
>> > d. Click Advanced.
>> > e. Click to select every checkbox here.
>> > f. Click OK to close these windows.
>> > g. Reproduce this issue and send the logs to me.
>> >
>> > NOTE: The log files are located at %systemroot%\System32\LogFiles by
>> > default.
>> >
>> > Please compress all the files and send to me at v-jaluo@microsoft.com
>> >
>> > I appreciate your time and cooperation. Please do not hesitate to let
>> > me
>> > know if you have any further concerns, I am looking forward to hearing
>> > from
>> > you.
>> >
>> > Have a nice day!
>> >
>> > Best regards,
>> >
>> > Jacky Luo (MSFT)
>> > Microsoft CSS Online Newsgroup Support
>> >
>> > Get Secure! - www.microsoft.com/security
>> > ====================================================
>> > PLEASE NOTE: The partner managed newsgroups are provided to
>> > assist with break/fix issues and simple how to questions.
>> > We also love to hear your product feedback! Let us know what you think
>> > by
>> > posting
>> >
>> > from the web interface: Partner Feedback
>> > from your newsreader: microsoft.private.directaccess.partnerfeedback.
>> >
>> > We look forward to hearing from you!
>> > ====================================================
>> > When responding to posts, please "Reply to Group" via your newsreader
>> > so that others may learn and benefit from this issue.
>> > ====================================================
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> > ====================================================
>> >
>> >
>> >
>> >
>

Hi Claus,

Please search for "NetworkFusion" and look at the question with "Connect
Computer" in the title. I had the same problem... It seems to be the same on
all the new disks produced!

Robin.
--
Delivered By Messenger Pigeon


"Claus" wrote:

> Hi All,
>
> SBS2003 R2 Premium, straight forward new install. Everything is running
> fine. No errors on any of the eventlogs. Trying to run connectcomputer we
> get a "page cannot be displayed" on http but we can get there with https.
> The login window comes up, the users and computers to pick from come up, the
> summary page comes up, but when we hit the last button, we are getting an
> error message that the installation encountered an error. Below is the link
> to join again and we can start all over with the same result.
>
> There are no error messages in the server eventlog. ISA monitoring doesn't
> display any error. We checked the virtual directory and it is not set to
> require SSL. All NIC cards (except one) are disabled on the client computer
> (XP Pro), firewall is disabled and antivirus is uninstalled.
>
> Has anybody seen this before?
>
> Thanks
>
> --
> Claus
>
>
>

Thanks Robin,

That explains a lot. I wonder what the heck MS is thinking implementing this
on a default SBS installation and not publishing any info on it.


--
Claus
"NetworkFusion" <NetworkFusion@discussions.microsoft.com> wrote in message
news:97822CD8-9F66-4B60-868A-03118029A5CD@microsoft.com...
> Hi Claus,
>
> Please search for "NetworkFusion" and look at the question with "Connect
> Computer" in the title. I had the same problem... It seems to be the same
> on
> all the new disks produced!
>
> Robin.
> --
> Delivered By Messenger Pigeon
>
>
> "Claus" wrote:
>
>> Hi All,
>>
>> SBS2003 R2 Premium, straight forward new install. Everything is running
>> fine. No errors on any of the eventlogs. Trying to run connectcomputer we
>> get a "page cannot be displayed" on http but we can get there with https.
>> The login window comes up, the users and computers to pick from come up,
>> the
>> summary page comes up, but when we hit the last button, we are getting an
>> error message that the installation encountered an error. Below is the
>> link
>> to join again and we can start all over with the same result.
>>
>> There are no error messages in the server eventlog. ISA monitoring
>> doesn't
>> display any error. We checked the virtual directory and it is not set to
>> require SSL. All NIC cards (except one) are disabled on the client
>> computer
>> (XP Pro), firewall is disabled and antivirus is uninstalled.
>>
>> Has anybody seen this before?
>>
>> Thanks
>>
>> --
>> Claus
>>
>>
>>

Hi Claus,

Have you wiped out and rebulit the server? can the issue reoccur?

I am just writing to see how everything is going. If you have any updates
or need any further assistance on this issue,please feel free to let me
know.I am glad to be of assistance. :-)


Best regards,

Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================

Jacky,

See the post above yours. The solution is to undo the strict RPC in ISA.

--
Claus
""Jacky Luo [MSFT]"" <v-jaluo@online.microsoft.com> wrote in message
news:2plbCKpdHHA.6068@TK2MSFTNGHUB02.phx.gbl...
> Hi Claus,
>
> Have you wiped out and rebulit the server? can the issue reoccur?
>
> I am just writing to see how everything is going. If you have any updates
> or need any further assistance on this issue,please feel free to let me
> know.I am glad to be of assistance. :-)
>
>
> Best regards,
>
> Jacky Luo (MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ====================================================
> PLEASE NOTE: The partner managed newsgroups are provided to
> assist with break/fix issues and simple how to questions.
> We also love to hear your product feedback! Let us know what you think by
> posting
>
> from the web interface: Partner Feedback
> from your newsreader: microsoft.private.directaccess.partnerfeedback.
>
> We look forward to hearing from you!
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader
> so that others may learn and benefit from this issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ====================================================
>

Hi Claus,

Thanks to posting back.


As you said,The solution is to undo the strict RPC in ISA.
can I confirm with you that you have found the roor cause is related to RPC
rule in ISA?

can you access by http://servername/connectcomputer and
https//servername/connectcomputer now?

By default,it should be accessed by http://servername/connectcomputer

Best regards,

Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================

Hi Jacky,

3 months after the post I had to first think about what you were referring
to. We did rebuild that server and were not able to reproduce the issue, nor
could we find any reasonable explanation.

--
Claus
""Jacky Luo [MSFT]"" <v-jaluo@online.microsoft.com> wrote in message
news:2plbCKpdHHA.6068@TK2MSFTNGHUB02.phx.gbl...
> Hi Claus,
>
> Have you wiped out and rebulit the server? can the issue reoccur?
>
> I am just writing to see how everything is going. If you have any updates
> or need any further assistance on this issue,please feel free to let me
> know.I am glad to be of assistance. :-)
>
>
> Best regards,
>
> Jacky Luo (MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ====================================================
> PLEASE NOTE: The partner managed newsgroups are provided to
> assist with break/fix issues and simple how to questions.
> We also love to hear your product feedback! Let us know what you think by
> posting
>
> from the web interface: Partner Feedback
> from your newsreader: microsoft.private.directaccess.partnerfeedback.
>
> We look forward to hearing from you!
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader
> so that others may learn and benefit from this issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ====================================================
>