Jan said:
Hi
I appreciate the help, I seem to be go in circles and they are not
seemingly decreasing!
Stop. Just stop that.
Last night in an attempt to re-create an earlier working environment I
changed the isaserver from being part of the domain to being part of
'workgroup', now I get errors when trying to be part of the domain again
Likely flailing -- and you cannot use the ISA to give different privileges
(net access) to Domain users based on ID or group.
I also worked through the isaserver settings for the connections tcp/ip
properties, dns and dchp settings, setting them all back to the original
values as per instructions.
I set the server1 forwarders to 10.10.1.99 (isaserver) as you suggested.
That is one choice. For this to work, you should be able to go to
Server1 command line and Nslookup (something on the Internet)
by using 10.10.1.99 explicitly:
nslookup
www.google.com 10.10.1.99
If this works then server1 CAN use ISA to resolve the Internet AND
ISA can in fact resolve the Internet.
If this fails, then one of those is (part of) the problem.
I do seem to be able to ping google again!
but in my client if i set
the LAN option and the proxy server settings i still get a page saying
about dns errors
"If I set the LAN option" -- What specifically do you mean?
Are you having trouble getting web pages in your browser when
it is set to use the Proxy/ISA server AND yet able to resolve the names
using DNS (nslookup)?
If so that is almost certainly an ISA (as a security server) issue unless
you have messed up the Client (IE) proxy settings.
I'm still learning about networks so i didnt know about nslookup
That should be
-- you learned something that is GENERALLY useful,
not just useful in this specific case.
I have done the nslookups you suggest, not sure why i get the domain
doesnt exist errors, or how to procede? Any further help is much
appreciated
here is what i get:
from server1:
ipconfig /all shows:
You didn't copy and past in the text but typed it in yourself -- don't
do that -- YOUR idea of what is important or any errors you
introduce just confuse the problem.
ip config
host name: server1
primary dns suffix: study.local
dns suffix search list study.local
Local adapter
DHCP Enabled: NO (I have disabled it and transfered autheroty to
isaserver)
What does that ("I have disabled...") mean? DHCP enable means
that this CLIENT is not a DHCP client.
ip address 10.10.1.1
subnet 255.0.0.0
Odd choice for subnet mask but legal, and possibly correct.
Wrong UNLESS you don't want the DC (server1) to EVER
visit the Internet (except for proxy controlled things, so you
might actually use this.) More common would be to use the
ISA address here too.
dns server 10.10.1.1
Correct.
nslookup
www.google.com 10.10.1.1
***Cant find server name for address 10.10.1.1: non existant domain
These reverse "errors" are ENTIRELY BOGUS artifacts of the
way that NSLookup operates --- IGNORE THESE if you get your
'actual question answered' such as down below....
server: unknown
address: 10.10.1.1
Non Autherative answer:
name:
www.l.google.com
Address: 216.239.59.104 (and a whole bunch more)
Aliases:
www.google.com
Name resolution works. You don't have an apparent DNS issue for
the Internet using ISA.
nslookup
www.google.com 10.10.1.99
***Cant find server name for address 10.10.1.99: non existant domain
server: unknown
address: 10.10.1.99
Non Autherative answer:
name:
www.l.google.com
Address: 216.239.59.104 (and a whole bunch more)
Aliases:
www.google.com
Name resolution works. You don't have an apparent DNS issue for
the Internet using itself (server1) either.
nslookup
www.google.com 195.92.195.94 (apparantly my isp's dns server)
***Cant find server name for address 195.92.195.94: no responce from
server
server: unknown
address: 195.92.195.94
***unknown cant find
www.google.com : no reponse from server
This makes sense and means your DC (server1) cannot access the ISP
DIRECTLY but must use the ISA -- which is probably the RIGHT thing
to do.
From my ISA server I get:
ipconfig /all shows:
ip config
host name: isaserver
primary dns suffix: study.local
dns suffix search list study.local
ethernet adapter on local connection
DHCP enabled: no
ip address 10.10.1.1
subnet 255.0.0.0
default gateway 'blank'
Odd. This should be set on the external interface to point to the ISP
ROUTER.
Oddly enough, this should be set to Server1 IF you want ISA to be
a member of the domain (and be able to fully use it's security.)
VERY few people understand this very trick point.
nslookup
www.google.com 10.10.1.1
***Cant find server name for address 10.10.1.1: non existant domain
server: unknown
address: 10.10.1.1
Non Autherative answer:
name:
www.l.google.com
Address: 216.239.59.104 (and a whole bunch more)
Aliases:
www.google.com
Thinks are working for DNS.
nslookup
www.google.com 10.10.1.99
***Cant find server name for address 10.10.1.99: non existant domain
server: unknown
address: 10.10.1.99
Non Autherative answer:
name:
www.l.google.com
Address: 216.239.59.104 (and a whole bunch more)
Aliases:
www.google.com
Means it will work even if you change the DNS setting to
point to the INTERNAL DNS (server1) as I suggested above.
nslookup
www.google.com 195.92.195.94 (apparantly my isp's dns server)
server: resolver1.svr.pol.co.uk
address: 195.92.195.94
Non Autherative answer:
name:
www.l.google.com
Address: 216.239.59.104 (and a whole bunch more)
Aliases:
www.google.com
Fine. Means we can get directly to the ISP from the ISA but that
was pretty much a given since everything else was already shown to
work.
From my client pc I get:
ipconfig /all shows:
ip config
host name: pc2
primary dns suffix: study.local
dns suffix search list study.local
Local adapter
DHCP Enabled: yes
ip address 10.10.1.2
subnet 255.0.0.0
default gateway 'blank'
dhcp server: 10.10.1.99
dns server 10.10.1.1
nslookup
www.google.com 10.10.1.1
***Cant find server name for address 10.10.1.1: non existant domain
server: unknown
address: 10.10.1.1
Non Autherative answer:
name:
www.l.google.com
Address: 216.239.59.104 (and a whole bunch more)
Aliases:
www.google.com
nslookup
www.google.com 10.10.1.99
***Cant find server name for address 10.10.1.99: non existant domain
server: unknown
address: 10.10.1.99
Non Autherative answer:
name:
www.l.google.com
Address: 216.239.59.104 (and a whole bunch more)
Aliases:
www.google.com
nslookup
www.google.com 195.92.195.94 (apparantly my isp's dns server)
***Cant find server name for address 195.92.195.94: no responce from
server
server: unknown
address: 195.92.195.94
***unknown cant find
www.google.com : no reponse from server
DNS works. Don't mess with DNS except perhaps to have the ISA
use the Internal DNS (server1) as I suggested above.
