Strange Problem with DNS?

I have two separate getways that users can access the internet in my
network. Using the first gateway everything is fine, one the second if
users go to a specific website the page will load, once completed the user
is then redirected to a 404 page not found error. This is only happening on
one specific website, but the issue is not with that site as I can access it
without a problem when I use a computer that is in the same domain, but uses
a different gateway.

I'm really stumped on this and don;t even know where to begin to look. Any
help would be appreciated. I can provide more details, but I don't even now
where to begin.

Thank you,

Chuck

Your DNS Scheme is probably to blame.

All machines (*all*) on the LAN must use the AD/DNS Server for DNS
Resolution. If there is more than one, add them all to the list. The ISP's
DNS IP#(s) get listed in the Forwarders List in the config of the AD/DNS
service. If there is more than one AD/DNS, repeat the config on all of them.
This is the only place the ISP's DNS should ever appear. The AD/DNS
machine(s) then needs to ability to make outbound DNS queries through
whatever you use for a firewall/proxy.

There is pretty much little to no flexabiltiy on this,...if you want it to
work right,..this is the way it must be.

The number of gateways and/or how they are used is irrelevant.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"ChuckMcGuire" <chuck.mcguire(remove)@radisson.com> wrote in message
news:(E-Mail Removed)...
>I have two separate getways that users can access the internet in my
>network. Using the first gateway everything is fine, one the second if
>users go to a specific website the page will load, once completed the user
>is then redirected to a 404 page not found error. This is only happening
>on one specific website, but the issue is not with that site as I can
>access it without a problem when I use a computer that is in the same
>domain, but uses a different gateway.
>
> I'm really stumped on this and don;t even know where to begin to look.
> Any help would be appreciated. I can provide more details, but I don't
> even now where to begin.
>
> Thank you,
>
> Chuck
>

Thank you for the reply,

The problem has now fixed itself without making any changes. All
workstation do use the same DNS server.


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> Your DNS Scheme is probably to blame.
>
> All machines (*all*) on the LAN must use the AD/DNS Server for DNS
> Resolution. If there is more than one, add them all to the list. The
> ISP's DNS IP#(s) get listed in the Forwarders List in the config of the
> AD/DNS service. If there is more than one AD/DNS, repeat the config on all
> of them. This is the only place the ISP's DNS should ever appear. The
> AD/DNS machine(s) then needs to ability to make outbound DNS queries
> through whatever you use for a firewall/proxy.
>
> There is pretty much little to no flexabiltiy on this,...if you want it to
> work right,..this is the way it must be.
>
> The number of gateways and/or how they are used is irrelevant.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> "ChuckMcGuire" <chuck.mcguire(remove)@radisson.com> wrote in message
> news:(E-Mail Removed)...
>>I have two separate getways that users can access the internet in my
>>network. Using the first gateway everything is fine, one the second if
>>users go to a specific website the page will load, once completed the user
>>is then redirected to a 404 page not found error. This is only happening
>>on one specific website, but the issue is not with that site as I can
>>access it without a problem when I use a computer that is in the same
>>domain, but uses a different gateway.
>>
>> I'm really stumped on this and don;t even know where to begin to look.
>> Any help would be appreciated. I can provide more details, but I don't
>> even now where to begin.
>>
>> Thank you,
>>
>> Chuck
>>
>
>

OK..

Phil


"ChuckMcGuire" <chuck.mcguire(remove)@radisson.com> wrote in message
news:(E-Mail Removed)...
> Thank you for the reply,
>
> The problem has now fixed itself without making any changes. All
> workstation do use the same DNS server.