Archived from groups: microsoft.public.win2000.dns (
More info?)
Sorry for the jumping around. The application/website is internal and
external. The box that the app is running on is fully contained. Win2003
Server, SQL, IIS, SSL. It is not a part of our corp. domain, it is a stand
alone workgroup. The name is https://cash.thefloridacenter.org.
In DNS, which is sitting on our domain, it is under the corp domain zone and
the FQDN is thefloridacenter.org. That is where I am confused because that
is not right, that machine is not a part of the domain. Internally though,
everything is working with DNS. I ran a FreePing all weekend and never had a
problem getting to the box by name or by IP.
On a side note, this server used to be a part of the domain with the same
server name. Is it possible that DNS still thinks it is a part of the domain?
I hope this clears it up a little...very sorry for the confusion.
Thank you very much for your help and time.
Joan
"Ace Fekay [MVP]" wrote:
> In news:3546D527-BE81-433A-A229-D2F249A299AD@microsoft.com,
> Joan <Joan@discussions.microsoft.com> made a post then I commented below
> > We have a Windows 2003 domain. There is also have a stand alone (not
> > a part of the domain) windows 2003 server. I have that server
> > pointing to my primary DNS in my domain. When you look at the host
> > record it has the fully qualified domain but that is not correct
> > because that server is not a part of the domain. Should I put DNS on
> > the stand alone box then point the primary to itself and the
> > secondary DNS to the domain.
> >
> > We am experiencing inconsistent problems with page not found errors
> > in the web based application that is sitting on this stand alone box.
> > I have tested all hardware.
> >
> > Thanks for any help!
>
> It is somewhat difficult to follow your post, it jumps around a bit, and is
> doesn't provide any specific information with what you are tyring to do and
> what is exactly happening, to help you, which is probably why no one else
> has responded yet.
>
> What exactly are you trying to accomplish or connect to? Is it an external
> website or an internal website? Is the website you are trying to connect to
> on this 2003 standalone machine (assuming IIS is installed and operational)
> or another machine? What is the name of the website? Does that FQDN exist in
> your DNS? Is it hostheader based?
>
> We'll need more specific info to better help.
>
>
> --Â?
> Regards,
> Ace
>
> Please direct all replies ONLY to the Microsoft public newsgroups
> so all can benefit.
>
> This posting is provided "AS-IS" with no warranties or guarantees
> and confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft Windows MVP - Windows Server - Directory Services
>
> Security Is Like An Onion, It Has Layers
> HAM AND EGGS: A day's work for a chicken;
> A lifetime commitment for a pig.
> --Â?
> =================================
>
>
>