Not able to ping machines in same domain while using a DNS Suffix Search List

We are using a .vbs script to configure our client dns suffix search lists.  I have found that while using a dns suffix search list, the primary DNS suffix is not used.  I have manually added the primary DNS suffix search list to the script however that dns suffix does not 'stick'.  The only way I have found to connect to a machne in my domain is by using the FQDN.  Here is an example.
We are running 2003 AD
The domain I am in is
The DNS suffixes in the seach list .vbs script are:
I can ping anything in and by using host name only.  I cannot ping anytihing in unless I use the FQDN.  
I have tried entering manually in my DNS suffix search list to no avail.  An ipconfig /all shows my Primary DNS as and & show in the DNS suffix search list.  Wierd...
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.

Jared LukerCommented:
Sounds like a DNS problem to me.  Are you sure your reverse lookup zones are configured correctly?
Looks like a Browsing and DNS problem.   Make sure you don't have Netbios disabled on machines that require FQDN.  Install a WINS server and set all the machines to use it for the WINS server.  
billzbubsAuthor Commented:
I am trying to resole host name to IP not IP to host name so it is not a revers DNS issue.  One of the great points of DDNS is to get rid of crappy WINS so that is not an option either.
ON-DEMAND: 10 Easy Ways to Lose a Password

Learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees in this on-demand webinar. We cover the importance of multi-factor authentication and how these solutions can better protect your business!

Jared LukerCommented:
Are you able to use NSLOOKUP at all?
billzbubsAuthor Commented:
OK, I found it.  It was a 2003 Group Policy that was stepping on the .vbs script.  Since the GPOs in 2003 to configure DNS Suffix Search lists only work on XP/2003 clients, we will have to use St. Bernard to deploy the .vbs script only to our W2K clients and rely on 2003 GPOs to hook up the XP and 2003 machines.  thanks for the assistance anyway.
PAQed with points refunded (300)

Community Support Moderator

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
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

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.