DNS & AOL

  • Thread starter Thread starter Dave
  • Start date Start date
D

Dave

I have 3 servers, two Win2000 Active directory and one
NT4.0 Exchange. I have two users that use AOL on their
PC's via isp/lan connection. My network has a Sonicwall
firewall that also allows a remote office with a
Sonicwall to connect to our network. Active directory
was implemented last year and AOL for the two users has
been fine. Started getting 'ISP/Lan connection unable to
connect' messages when users tried to access their AOL
accounts. No other problems on the network and could
even get to the www.aol.com web page. DHCP is setup
correctly and gives out the Dns address of my internal
servers. I found that if I hard code the ISP's DNS
servers on these two PC's the problem will disappear.
Any DNS guru's that could help would be appreciated.
Thank you. Dave
 
In
posted their thoughts said:
I have 3 servers, two Win2000 Active directory and one
NT4.0 Exchange. I have two users that use AOL on their
PC's via isp/lan connection. My network has a Sonicwall
firewall that also allows a remote office with a
Sonicwall to connect to our network. Active directory
was implemented last year and AOL for the two users has
been fine. Started getting 'ISP/Lan connection unable to
connect' messages when users tried to access their AOL
accounts. No other problems on the network and could
even get to the www.aol.com web page. DHCP is setup
correctly and gives out the Dns address of my internal
servers. I found that if I hard code the ISP's DNS
servers on these two PC's the problem will disappear.
Any DNS guru's that could help would be appreciated.
Thank you. Dave

Check the setting for "Secure Cache against Pollution in your DNS server's
properties. This seems to be the problem du jour lately. This should help
you.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
I just recently had the same problem over the past few
days, AOL was not much help!!! they claimed that it was a
packet issue and that there were not enought packets
passing through our gateway. I called our ISP and this
was not the case. I temporarily resolved the issue by
restarting my DHCP and DNS services. So far, I have not
had any other occurrances

I HOPE THIS HELPS

REGARDS,
 
Back
Top