> Read inline please.
>
> In news:1756BB58-06E5-42B5-BCB9-123FD00E568D[ at ]microsoft.com,
> P J Bryant <PJBryant[ at ]discussions.microsoft.com> typed:
> > I know there's lots of info missing, but i'm looking for a prod in
> > the right direction at the moment, rather than a specific fix!
> >
> > New network, just three boxes for now, DC, Domain-joined ISA box
> > (dual NIC, external connection to ADSL router), member server (for
> > VM). Servers are bog standard HP DL, fully up to date with firmware,
> > and WIndows 2003 SP2 server installed via HP tools (so correct
> > drivers loaded)
> > * DHCP and DNS setup and running (more later though)
> > * ISA Server configured for discovery and working
> > * NSLOOKUP working fine.
> > * Internet browsing through ISA all OK (using ISA client on machines)
> > * DHCP allocation to client all OK and the ISA WPAD entry is clearly
> > working.
> >
> > Not working:
> > * login times (except on DC) taking ages
> > * remote authentication requests (for share permissions say) timing
> > out (errors in log - [sorry away from site so no eventid right now]
> > which report unable to authenticate, kerberos
> > * DNS updates to the forward lookup zone (unless I allow non-secure
> > updates when the HOST records are then entered).
> >
> > It feels (and I stress feels!) like a firewall is in the way on the
> > DC. But there nothing there to do that. Done plenty of googling,
> > and nothing obvious comes to light.
> >
> > My one concern is that the HP teamed NIC might be doing something, so
> > will break the team next time I'm there, disable a NIC, and use a
> > single NIC with the same IP settings.
> >
> > It's the sort of setup that works every time <g> and you can do in
> > your sleep <bg> but this time is not, and there's nothing I've done
> > that various from the normal.
> >
> > So if you have any suggestions please shout out!
> >
> > Thanks, Peter
>
> Long logon times typically indicate that you have incorrectly used a DNS
> server in TCP/IP properties that does not support the AD domain. All DNS
> servers listed in TCP/IP properties, on any NIC on an AD domain member must
> support and resolve the AD domain.
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
>
http://www.lonestaramerica.com/>
http://support.wftx.us/>
http://message.wftx.us/> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
>
http://home.in.tum.de/~jain/software/oe-quotefix/> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
>
http://www.oehelp.com/OEBackup/Default.aspx> ===================================
>
>
>