accessing our own website SBS 2003 R2

Hi Guys
for quite a while we have not been able to access our own external website,
from the server or any of the clients, it just comes up page can not be
displayed. thie web address is the same as our server domain name. we can
access the internal companyweb.
Any ideas where i can start to try and solve this?
Thanks in advance.
Chris

What is your internal AD domain name? What is your external domain name used
by the website?

"Chris" <> wrote in message
news:51A6B71D-1A81-4A40-8B4E-...
> Hi Guys
> for quite a while we have not been able to access our own external
> website,
> from the server or any of the clients, it just comes up page can not be
> displayed. thie web address is the same as our server domain name. we can
> access the internal companyweb.
> Any ideas where i can start to try and solve this?
> Thanks in advance.
> Chris

Both domain names are exactly the same.
I just found out that on each client network adapter the primary dns points
back to the servers IP address, if i change this to our ISP's dns server then
i can get the external site but lose the internal.


"SteveB" wrote:

> What is your internal AD domain name? What is your external domain name used
> by the website?
>
> "Chris" <> wrote in message
> news:51A6B71D-1A81-4A40-8B4E-...
> > Hi Guys
> > for quite a while we have not been able to access our own external
> > website,
> > from the server or any of the clients, it just comes up page can not be
> > displayed. thie web address is the same as our server domain name. we can
> > access the internal companyweb.
> > Any ideas where i can start to try and solve this?
> > Thanks in advance.
> > Chris
>
>
> .
>

Chris wrote:
> Both domain names are exactly the same.
> I just found out that on each client network adapter the primary dns points
> back to the servers IP address, if i change this to our ISP's dns server then
> i can get the external site but lose the internal.
>
>
Don't even think about that. A Microsoft AD network requires that only
an AD-aware DNS server ever be used. Your original configuration is the
only correct one. Don't use outside DNS servers as secondaries, either.

Quick fix: a hosts file entry for your web server. Better: an entry for
it in your DNS server. Better still, and too late now, was not to use a
publicly-valid name for your SBS domain. This is one of the reasons.

--
Joe

In article <6B7A0E3F-237D-4DED-854F->,
says...
> Both domain names are exactly the same.
> I just found out that on each client network adapter the primary dns points
> back to the servers IP address, if i change this to our ISP's dns server then
> i can get the external site but lose the internal.
>

Create a WWW entry in your DNS and point it to the IP of your external
web server.

The SBS server MUST ALWAYS BE YOUR ONLY DNS SERVER.

Your issues is why you never name your AD Domain the same as your
external domain name.



--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)

Thanks for the help guys, any idea where i can find a document to explain how
to
do either of those fixes ("a hosts file entry for your web server. Better:
an entry for
> it in your DNS server.)
Im not at all familiar with those procedures, the aim is to be able to
access our internal and external company web sites
Thanks again
Chris
"Joe" wrote:

> Chris wrote:
> > Both domain names are exactly the same.
> > I just found out that on each client network adapter the primary dns points
> > back to the servers IP address, if i change this to our ISP's dns server then
> > i can get the external site but lose the internal.
> >
> >
> Don't even think about that. A Microsoft AD network requires that only
> an AD-aware DNS server ever be used. Your original configuration is the
> only correct one. Don't use outside DNS servers as secondaries, either.
>
> Quick fix: a hosts file entry for your web server. Better: an entry for
> it in your DNS server. Better still, and too late now, was not to use a
> publicly-valid name for your SBS domain. This is one of the reasons.
>
> --
> Joe
> .
>

In article <C9590BD5-FF2E-4EC7-BE27->,
says...
> Thanks for the help guys, any idea where i can find a document to explain how
> to
> do either of those fixes
>

The DNS entry in your servers DNS Interface is the way to go - you don't
want to bother pushing out a HOST file to all of the workstations or
editing one on the server either.

I hate to say this, but, if you don't know where to find or how to add
DNS records to your SBS server it's time to call in a professional so
that you don't break anything.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)

and the best action to take at this time is to reinstall in a non-public
name space.

remaining with it, working around the problems, will bite you again.

"Leythos" <> wrote in message
news: om...
> In article <6B7A0E3F-237D-4DED-854F->,
> says...
>> Both domain names are exactly the same.
>> I just found out that on each client network adapter the primary dns
>> points
>> back to the servers IP address, if i change this to our ISP's dns server
>> then
>> i can get the external site but lose the internal.
>>
>
> Create a WWW entry in your DNS and point it to the IP of your external
> web server.
>
> The SBS server MUST ALWAYS BE YOUR ONLY DNS SERVER.
>
> Your issues is why you never name your AD Domain the same as your
> external domain name.
>
>
>
> --
> You can't trust your best friends, your five senses, only the little
> voice inside you that most civilians don't even hear -- Listen to that.
> Trust yourself.
> (remove 999 for proper email address)

Ok Thanks again

"Leythos" wrote:

> In article <C9590BD5-FF2E-4EC7-BE27->,
> says...
> > Thanks for the help guys, any idea where i can find a document to explain how
> > to
> > do either of those fixes
> >
>
> The DNS entry in your servers DNS Interface is the way to go - you don't
> want to bother pushing out a HOST file to all of the workstations or
> editing one on the server either.
>
> I hate to say this, but, if you don't know where to find or how to add
> DNS records to your SBS server it's time to call in a professional so
> that you don't break anything.
>
> --
> You can't trust your best friends, your five senses, only the little
> voice inside you that most civilians don't even hear -- Listen to that.
> Trust yourself.
> (remove 999 for proper email address)
> .
>