Weired DNS problem

I have a very strange problem. We have an ISA 2004 server and connect our
remote clients (XP sp1) through VPN. Everything is working fine (100 users)
but 5 of our clients have a DNS problem. When they try to connect to the
internal Exchange 2003 sp1 server (Outlook 2003 http/rpc and OWA) they always
get the external ip address resolved instead of the internal ip, but all
other internal server names are being resolved correct from the internal DNS
servers. We have examined the hosts file and it contains only 127.0.0.1, the
internal DNS server has no reference to external adresses and the routing
table on the client are routing all traffic though the VPN tunnell, we have
also tried ipconfig/flushdns, no difference, when we put in the internal ip
in the hosts file everything is working fine but this is of course not a
permanent solution - do you have any ideas what might cause this ?

Don't use FQDNs for the mail server. Always access it by the Netbios Name.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"Soren" <(E-Mail Removed)> wrote in message
news:4B5A46A4-4162-44F8-8880-(E-Mail Removed)...
> I have a very strange problem. We have an ISA 2004 server and connect our
> remote clients (XP sp1) through VPN. Everything is working fine (100
users)
> but 5 of our clients have a DNS problem. When they try to connect to the
> internal Exchange 2003 sp1 server (Outlook 2003 http/rpc and OWA) they
always
> get the external ip address resolved instead of the internal ip, but all
> other internal server names are being resolved correct from the internal
DNS
> servers. We have examined the hosts file and it contains only 127.0.0.1,
the
> internal DNS server has no reference to external adresses and the routing
> table on the client are routing all traffic though the VPN tunnell, we
have
> also tried ipconfig/flushdns, no difference, when we put in the internal
ip
> in the hosts file everything is working fine but this is of course not a
> permanent solution - do you have any ideas what might cause this ?

On 9/13/2005 06:30, Soren wrote:
> but 5 of our clients have a DNS problem. When they try to connect to the
> internal Exchange 2003 sp1 server (Outlook 2003 http/rpc and OWA) they always
> get the external ip address resolved instead of the internal ip

Maybe those clients are unwittingly also using dns servers from your ISP?

Good luck running an exchange server with a public IP.

~Jason

--

Still the same problem, if I'm using netbios name in outlook it is
automatically replaced with FQDN.

"Jason Gurtz" wrote:

> On 9/13/2005 06:30, Soren wrote:
> > but 5 of our clients have a DNS problem. When they try to connect to the
> > internal Exchange 2003 sp1 server (Outlook 2003 http/rpc and OWA) they always
> > get the external ip address resolved instead of the internal ip
>
> Maybe those clients are unwittingly also using dns servers from your ISP?
>
> Good luck running an exchange server with a public IP.
>
> ~Jason
>
> --
>