Automatic site code discovery was unsuccessful
Thorsten Basevi
we encountered an issue here that our clients in the central site cannot
auto discover the site code anymore.
We're having a central site and several secondaries in SMS 2003 SP3 . The ad
is extended and we're running in advanced security.
For luck the clients are still having their (old) entry of the site code and
seem to be running fine, but auto discover on the central site results in an
error message.
On the secondaries it works fine.
Strange thing is, that we're getting this error in locationservices.log for
auto discover on the central site
<![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="08:26:38.628+-60"
date="02-06-2009" component="LocationServices" context="" type="1"
thread="55348" file="lsad.cpp:2008">
<![LOG[Retrieved SLPs from AD]LOG]!><time="08:26:38.644+-60"
date="02-06-2009" component="LocationServices" context="" type="1"
thread="55348" file="lsad.cpp:2012">
<![LOG[Current AD site of machine is geerla01]LOG]!><time="08:26:38.706+-60"
date="02-06-2009" component="LocationServices" context="" type="1"
thread="55348" file="lsad.cpp:274">
<![LOG[Failed to send request to
/sms_slp/slp.dll?site&ad=geerla01&ip=10.200.42.0&ir=10.200.42.42 at host
AUSLYNCSM01]LOG]!><time="08:26:45.597+-60" date="02-06-2009"
component="LocationServices" context="" type="3" thread="55348"
file="ccmhttpget.cpp:674">
<![LOG[HTTP ERROR:
URL=http://AUSLYNCSM01/sms_slp/slp.dll?site&ad=geerla01&ip=10.200.42.0&ir=10.200.42.42,
Port=80, Code=12007,
Text=ERROR_WINHTTP_NAME_NOT_RESOLVED]LOG]!><time="08:26:45.597+-60"
date="02-06-2009" component="LocationServices" context="" type="1"
thread="55348" file="ccmhttperror.cpp:121">
The problem is not the response, but the question the client is asking,
because
it's asking a server in our ad which is neither in our (sub-) domain nor in
our SMS architecture (of our country/region). That's a server from the US and
we're working in Germany. Those are two totally different SMS systems.
We're not connected in SMS and we're not having a common central
site....(????)
Does anyone exactly know how the clients are retreiving the servername to
ask for their assignement (in AD)? It's not using a FQDN so where does it get
it's information?
What we did so far:
We ran mptroubleshooter in post-installation mode. Only error was mpcert http
So I ran http://egeer00sm01.edom.ad.corp/SMS_MP/.sms_aut?MPCERT
got a result (serveral numbers) so I assume it's working fine
Checked slp funcionality with, e.g.
http://egeer00SM01.edom.ad.corp/sms_slp/slp.dll?site&ad=geoffe01&ip=10.200.42.0&ir=10.200.42.42
The ad site is been served from a secondary site server. This works fine,
getting the correct site code as answer.
Running the same with the site code of our central site brings "No Results"
as message.
So we also checked hman.log and the systems container in ad.
Checked the site boundaries on our central site.
Even reinstalled the slp and the mp on the cenrtal site
Tried a reset of SMS and a reboot of the machine.
Got finally stuck and posted my problem here....
Any ideas?
Thanks for help in advance.
Best regards
Thorsten
Sherry Kissinger [MVP-SMS]
steps. Have you looked in WINS yet for that SLP entry?
--
Standardize. Simplify. Automate.
Thorsten Basevi
thanks for your answer.
And yes, I also checked WINS and even re-registered the server in there.
Even though I thought with SMS 2003 SP3 and extended AD and advanced
security it's not
necessary to use WINS anymore....
But maybe I'm wrong.
In the meantime, we opened a case at Microsoft.
I'll post the solution as soon as we find out.
Thorsten Basevi
thanks for your answer.
And yes, I also checked WINS and even re-registered the server in there.
Even though I thought with SMS 2003 SP3 and extended AD and advanced
security it's not
necessary to use WINS anymore....
But maybe I'm wrong.
In the meantime, we opened a case at Microsoft.
I'll post the solution as soon as we find out.
Thorsten Basevi
thanks for your answer.
And yes, I also checked WINS and even re-registered the server in there.
Even though I thought with SMS 2003 SP3 and extended AD and advanced
security it's not
necessary to use WINS anymore....
But maybe I'm wrong.
In the meantime, we opened a case at Microsoft.
I'll post the solution as soon as we find out.
amd
> AUSLYNCSM01]LOG]!><time="08:26:45.597+-60"
> date="02-06-2009"
> component="LocationServices" context="" type="3"
> thread="55348"
> file="ccmhttpget.cpp:674">
> <![LOG[HTTP ERROR:
>
> Port