Windows 2000 Server/Workstation Caching Issue

I have a Windows 2000 running Small Business Server. Desktops are W2K.

Trying to log onto a internet banking page that WAS accessable last Friday. There have been no changes made to our network. Spoke to the Bank and they said I have to refresh the DNS on the server.

Today, one of the workstations is able to access the site. But others still cannot.

I did the following on the Server and the Workstation that cannot connect:
ipconfig /release
ipconfig /renew
ipconfig /flushdns
ipconfig /registerdns
restarted pc

Still no luck.

I restarted the DNS Services on the server, then restarted the workstation. No luck.

Anyone have any suggestions?

Here is the link. Clicking on "Log In" times out.
http://www.nfbconnect.com/

Thanks in advance.
Greg
gsd0519Asked:
Who is Participating?
 
oBdAConnect With a Mentor Commented:
ipconfig /flushdns only clears the DNS *client's* cache. Your DNS server is caching lookups as well, and this is probably what's keeping you from getting the real IP.
On your DNS server, in a command window enter
dnscmd /clearcache
which should flush the DNS server's cache.
On another issue: Seeing that some clients get the correct IP leads me to believe that you have the ISP's DNS server in the TCP/IP settings on some or all clients? If so, change that, as it is as incorrect as can be in an AD domain.
On your DC/DNS, and on all of your domain members, make sure the DC's address *only* is listed in the TCP/IP properties (be that via DHCP or static; do NOT use 127.0.0.1 on the DNS itself!). That makes sure your internal lookups work correctly.
For internet access, delete the root zone (if present; it's the single dot: ".") on your DNS in your forward lookup zones. Then open the properties page of your DNS server and configure forwarders to point to your ISP's DNS. The forwarders section is the *only* entry in your network where your ISP's DNS should be listed.

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036

HOW TO: Troubleshoot DNS Name Resolution on the Internet in Windows 2000
http://support.microsoft.com/?kbid=316341

HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?kbid=300202
0
 
chadCommented:
you have one client pc that can access the website?
ping the website from the command prompt on that machine and note the IP address.
ping the website from a nonworking pc

then use the nslookup tool on both computers and report back on what you find
the proper IP should be 12.119.128.86
I can access the site but the ping fails... I am guessing they have ICMP blocks on  their firewall
good luck
0
 
chadCommented:
ok, maybe that IP does not work.
try this on a non-working client
http://12.111.47.207/
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
gsd0519Author Commented:
Request timed out.... on http://12.111.47.207
0
 
gsd0519Author Commented:
Just a reminder... ALL pc's CAN access the https://www.nfbconnect.com site, but ONLY 1 can get to Log In page. All are w2k.
0
 
gsd0519Author Commented:
the non working pc's nslookup:    66.252.170.3
the working pc's nslookup:    66.252.161.34

Does this mean anything??
0
 
chadCommented:
https://12.111.47.207/cashman/eCashmanSignon.Asp
ohhhh... ok.
If they could reach the main site but not the cashman section.  It may not be a dns issue
try the above link in a browser to see if it brings up the log on page

>>>the non working pc's nslookup:    66.252.170.3
>>>the working pc's nslookup:    66.252.161.34
are these the DNS server addresses that your computers are using? Are these from your ISP?
0
 
gsd0519Author Commented:
Restarted the server and one of the Non-working pc's now can connect.

Going to go to another non-working pc and see if a release/renew/flush/register/restart works.
0
 
gsd0519Author Commented:
Thank you all for your help. I restarted the Serverand magically that resolved the problem. I will keep this thread handy though for future use.

Is it possible to split the points?
0
 
chadConnect With a Mentor Commented:
Glad to see it is working again.  I would look into the comment that oBda made about your client's tcp/ip settings.  They should not have the ISP's DNS server anywhere in the settings.  Only the local DNS server.
Did you try the dnscmd /clearcache that oBda mentioned before restarting the server?  I think the restarting of the server would have effectively done the cache clear for DNS.
K

Is it possible to split points?  Yes use this link here
   |
   |
   V
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.