If a workstation is lauthenicated locally, then I am not able to go to the company's web site.

I am glad it jogs someone's memory, actually the issue is quite simple from what's happening. Here it is in a nut shell:
 
The server's domain name is www.abc.com, the alias or short name is "abc" for pre-Windows 2000 workstations. When a user authenticates into the www.abc.com  domain everything works.....EXCEPT when they try to go to abc's Web Site which is of course is www.abc.com . They receive an error of "URL or page not found". I believe what is happening, since they are logged in to a domain of www.abc.com at their local workstation, when they use their Internet Explorer and type in www.abc.com their browser becomes confused domain name wise and instead of going out on the internet it looks at the local domain and of course there is no Web Site locally....therefore the page or URL error.
 
The question then becomes, is there a way at either the server or the workstation that tells the workstation when it looks up www.abc.com to go outside the local network environment?
 
OH.......here's the catch and a good one at that.......there are many workstations at abc that do not yet authenticate into the local domain only attach......they have no problems finding the external www.abc.com Web Site. So, it appears authenticating is what causes the local workstation to become confused. As it sets the local domain of the workstation to www.abc.com ................. Ok there's the problem.....so is there an easy solution or
KNThomasonAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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

scampgbCommented:
Hi KNThomason,

It sounds like the internal DNS domain "abc.com" that is being used by the PCs as part of the Windows domain doesn't have an "A" record entry for the website.

The simplest solution is to create an "A" record on the internal Windows DNS server that has the IP address of your webserver.

I hope that this helps - let me know if you need any further help.

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
steinmtoCommented:
Scampgb's solution should work,  I have had to do this before.  A way to aviod this is to use the .local extension such as abc.local.
KNThomasonAuthor Commented:
I also have used the (.local) solution but I can not figure out how to implement it on a 2003 server.
scampgbCommented:
Hi - thanks for the "A".  Glad I could help :-)
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 Server 2003

From novice to tech pro — start learning today.