ISA Clients >> DNS problem with client.

by PeterD » Sat, 10 Sep 2005 23:41:38 GMT

(I'm just getting started with ISA, sorry if this is an obvious
question!)

ISA 2004 (test setup, simple two NIC as a NAT/Firewall configuration,
not much changed from how it was setup...)

Web pages open ok if I use IP addresses
Ping will ping either IP addresses or domain names
Web pages return DNS error (11001 error code) when a domain name is
used.

So IE won't use domain names, but ping will...

I'm missing the obvious, I think!

Suggestions?

ISA Clients >> DNS problem with client.

by PeterD » Sun, 11 Sep 2005 06:23:09 GMT



Interenting problem, but without any significant changes it began
working just fine... Sometimes you can't explain them, you just gotta
take what you get... <g>

Similar Threads

1. DNS problem: Outlook clients unable to reach Exchange

Dear all,

below is my scenario:
we have an exchange server on SBS 2003 configured with a private and a 
public interface (2 NIC + 2 IP addresses). The SBS is not in a DMZ, just 
direct to Internet. The public interface is registered to an ISP with the 
public mx-record.

Example:
Machine Domain= abc.local
Private Interface=192.168.0.1
Public Interface=111.111.111.111
Public mx-record=mx1.abc.com

When i try to use a client to ping abc.local, i sometimes get abc.local and 
sometimes 111.111.111.111

In the DNS, i can see 2 entries of A host records: 192.168.0.1 and 
111.111.111.111

From outlook client, when the server name is entered as mx1.abc.com, the 
name is later changed to abc.local.

When users are off site, using any Internet connection, they are unable to 
retrieve their emails, and he pinged abc. The result showed local, 192.168.0.1

this behaviour is inconsistent; Each time the dns is flushed, the identity 
of abc.local changes from 192.168.0.1 and 192.168.0.1

How can i changed the settings for the DNS to resolve this problem?
Also, how can i prevent users from contacting the exchange via the public IP 
address?
Thanx in advance

2. DNS problem when client is from VPN - Windows Small Business Server(SBS)

3. "Sendmail & Bind Problem" is actually a DNS Client library configuration problem

4. DNS Problems - BIND DNS server on linux, mainly windows XP clients

5. client access problem after changing dns settings

Last Friday we switched internet providers and updated all of the dns 
settings in our Exchange server. Since then, and not all the time, some 
clients are prompted for a user name and password when they open Outlook. If 
they type in the user name and password nothing happens - it doesn't accept 
the credentials. Sometimes if they reboot they can access Outlook without the 
logon box. For one client, it took nearly 5 reboots to get her computer to 
finally open up Outlook. 

There is nothing in the event log about bad logon attempts or anything. The 
only errors seem to be dns related and a problem with the smtp not connecting 
to the new dns addresses. I've verified the information again with our ISP 
and they claim everything is good on their end.

Exchange, dns and dhcp are running on the same server. Exchange is also a 
domain controller with the global catalog. 

Does anyone know what might be causing this? 

6. Client DNS problem

7. XP Client on 2000 Server - DNS problem?

I have a 2000 server with AD.  An XP client can not get to 
both the active directory and the Internet at the same 
time???

If I set the AD machine as the first entry in DNS, it can 
get to all shares, etc., but can then not get to 
Internet.  Similarly, if can see the internet, it can not 
see network drives.

Many 2000 workstations have no problems with the 2000 
server and AD.

Any help wold be greatly appreciated!!!!

Bob

8. DNS client srvice problem