Failed to resolve 'SMS_SLP' to IP address from WINS

Hi,
We have failed to image worksations in one of our sccm 2007 R2 sites. The initial troubleshooting showed that the workstation has failed at the stage of join to domain although the OS has been installed successfully. I noticed below errors from locationservice.log.
Assigning to site 'S01'
LSVerifySiteVersion
LSVerifySiteVersion : Verifying Site Version for <S01>
LSJoinedToADDomain
LSGetSiteVersionFromSLP
LSGetSLP
.....
Failed to resolve 'SMS_SLP' to IP address from WINS
LSGetSLP : Failed to resolve SLP from WINS, is it published
LSGetSiteVersionFromSLP : Unable to get the list of SLPs
LSVerifySiteVersion: Failed to get Site Version from AD and SLP

Open in new window


It seemed that the workstation failed to resolve name of SLP.

It was working fine back to few weeks ago and there were no major changes in our environment as far as I know.

I have googled the error and most of the results are talking about the scenario of using WINS which is not our case. We are not using WINS in our environment.

In our SCCM environment, the server locator point has been published to our Active Directory Domain Services, hence the client should automatically find a server locator point through Active Directory .
I don't know what has made the workstation tried to use WINS to locate SLP.

Just wondering if anyone could shed some light on it.

Many thanks.
LVL 1
brothertuAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

merowingerCommented:
WINS is the fallback method. Make sure the Client gets the SLP from AD. Check out the publishing there
0
brothertuAuthor Commented:
Thanks Merowinger.
That's what I wanted to figure out: what exactly should I do to check if SLP has been published properly in AD.

I have checked from Active Directory:
Domain name -> system -> system management

And I can see the SLP has been configured there.

Not sure if there is anywhere else should I check from AD.
0
merowingerCommented:
Now goto your Configmgr Client in Client's Control Panel and check if you can lookup your site
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

brothertuAuthor Commented:
The problem I am facing is, the workstation I wanted to reimage has failed to join to domain during the imaging process hence I am not able to logon to them due to our security restriction (which has disabled local admin logon ability).

There were some existing "good" workstations in this that have been imaged few weeks ago successfully. If I check the configmgr client from them then I can see the correct site code.
0
merowingerCommented:
Can you post the other Client Logs like ClientLocation.log, etc.
0
brothertuAuthor Commented:
The clientlocation.log has only one line:
Getting Assigned Site
0
brothertuAuthor Commented:
Just an udpate:
I've collected %systemroot%\debug\netsetup.log file and noticed it was empty.
That indicated something wrong with the local network.
Then I asked to check LAN switches and VLAN settings etc. It ended with a misconfiguration on the switch: "port fast" was not configured.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
brothertuAuthor Commented:
The lesson learned was that, if port fast is not configured on the router/switch then it may cause client to receive DHCP IP after a reboot with a little bit delay especially. And that was the root cause make the sccm client failed to locate servers during the imaging process.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.