Re: Single 2003 Server with DHCP, DNS and ISA 2006

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance




"Andy" <Andy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2CA88E24-C6AD-409E-9A5A-59B385833692@xxxxxxxxxxxxxxxx
Thanks again Herb for your help so far. It really is a great help.

At http://www.microsoft.com/technet/isa/2006/system_policy.mspx it
mentions
that System Policies are enabled on a default installation i.e DHCP, DNS
etc
but they didn't seem to get applied. As soon as I created my own DHCP
Request and Replies, DNS and LDAP rules the workstation was able to get an
IP
address.

I consider this to be a Black Art within ISA -- there is however an
EXCELLENT
set of ISA groups on the Microsoft newsgroups where you should ask you
ISA specific questions.

People who are truly expert and either use or teach each ever day will
answer your questions.

I was then able to be prompted for username and password when I tried to
join the workstation to the server but after a while it came up with
Network
path not found.

Sounds like DNS. The stations must use ONLY the internal DNS which
can find your DCs records.

DHCP should provide this and you can confirm with "IPConfig /all"
from a typical workstation.

Also, you should be able to pass a complete "DCDiag /c" with no FAIL
or WARN messages.

You DC is an "Internal DNS client" also, and must use ONLY the internal
DNS (itself likely).

I can ping the server by IP address and name from the workstation. The
other way round doesn't work yet though, I am sure I have to create
another
access policy.

Probably but pinging workstations by name is not usually essential.

I don't understand why I have to create these access rules when there are
default system policy rules though. Need to do more reading.

Magic. Black Magic.



.



Relevant Pages

  • Re: DHCP not working right after server restore from backup
    ... The whole problem seemed to be linked to old information in both DHCP and ... But from your message (the part about the DNS) I got the bright idea ... Make sure you do not test from just one workstation. ... from the server then I know thew network is goofed up. ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: dhcp not matching DNS
    ... What we are finding is the client will get a lease and you check dns ... and it does not match what was given by dhcp. ... To elaborate on scavenging and DnsUpdateProxy group that Meinolf mentioned, please read the following to gain a better understanding of how the whole thing works. ... Force DHCP to register all records, Forward and PTR, (whether a client ...
    (microsoft.public.windows.server.dns)
  • Re: Duplicate HOST A record entries on the reverse lookup Zone
    ... then 24 and did the manual/ start scavenging of the stale resource records ... Used the DHCP server to update DNS records: ... "Set Aging/Scavenging for All Zones. ...
    (microsoft.public.windows.server.dns)
  • RE: Remote Access Issue
    ... the DHCP server do not update the A record for the ... Click DNS ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)