SMS 2003 - Client site assignment connection problems....

have a 2003 site setup with just one site server/management point.  About
75% of my clients installed properly and are working correcty but about 25%
of them have a Locationservices.log file that looks like this.

<![LOG[Assigning to default Management Point '24.198.161.208']LOG]!>
<![LOG[Attempting to retrieve default management point from AD]LOG]!>
<![LOG[Attempting to retrieve default management point from WINS]LOG]!>
<![LOG[Attempting to retrieve NLB default management point from WINS]LOG]!>
<![LOG[Failed to resolve IP address from WINS]LOG]!>
<![LOG[No NLB default management point is present, attempting to resolve
default management point from WINS]LOG]!>
<![LOG[Retrieved Default Management Point through WINS:
24.198.161.208]LOG]!>
<![LOG[Persisting the default management point in WMI]LOG]!>
<![LOG[Persisted Default Management Point Location locally]LOG]!>
<![LOG[Failed to send request to /SMS_MP/.sms_aut?MPKEYINFORMATION at host
24.198.161.208]LOG]!>
<![LOG[HTTP ERROR: 12029 : ERROR_WINHTTP_CANNOT_CONNECT]LOG]!>

Now.. the big problem with this is.. my management point is not
24.198.161.208.. It just so happens that that IP is located somewhere in
maine and im over here in CA.. So i've not a clue where these computers are
getting this from.  I have tried uninstalling the client and reinstalling it
and the same computers seem to pull that same IP everytime..!  I checked
WINS and there is nothing in the wins database that matches that IP....
Also on any computer if I try and use the Discover button to automatically
find the site code it says Automatic Discovery was unsuccessful.
LVL 1
nwalterAsked:
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.

nwalterAuthor Commented:
Thanks.  I've since figured this out.  Can I answer my own question?

Should anyone stumple across this here is what happened:

Initially I figured out that removing netbeui protocol from the affected clients resolved the problem for that one client.  Upon further examination I found that removing the netbeui protocol from the server resolved it for all addected workstations regardless of weather or not they had netbeui installed.  I was able to reproduce this on a fresh install also so it appears to be a conflict with netbeui, microsoft said they would look into this have not seen anything come of it thou.
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
chadCommented:
excellent, what I will do move to have the question closed and points refunded to you. gl
KaBaaM
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
Windows Networking

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.