When I attempt to repair my internet connection by right-clicking on the tray icon and selecting "Repair" I get the following error when the process reaches the DNS flush stage:

"Windows could not finish repairing the problem because the following action cannot be completed:
Clearing the DNS cache

For assistance, contact the person who manages your network."

Well, I contacted myself, but I wasn't home

I tried flushing the DNS cache manually by going through the Start > Run... > CMD > ipconfig /flushdns approach, but I received yet another error:

"Could not flush the DNS Resolver Cache: Function failed during execution."

I also read Microsoft's solution to the problem, but it didn't work. They suggested that my DNS Client service was not running, but it was/is - and I've tried restarting the service, restarting the system, rebooting my router, and wiggling the power cable. Nada.

Any ideas?

Cheers.

Hi Paddy

I have been having exactly the same problem. Did you managed to resolve your problem?

regards
Shane

Sorry man, I haven't been able to fix it.

If anyone else on the forum would like to pitch in, Shane and I would be very grateful!

Hi

What address have you for DNS. You said you have router, is that an ADSL Router?

If so, try setting the IP to the Router IP, or loopback address 127.0.0.1

GL, David

Hello Marty

Yes, it is an ADSL router. I have set up a static IP address for the purposes of port forwarding, although my actual WAN IP is dynamic.

Now, when you say that I should set the IP to match the router's IP, which IP do you mean? Do you mean that I go into the internet connection settings and then into the "Intenet Protocol" bit, where the IP, Subnet Mask and Default Gateway settings are? If so, I've already altered those entries for the port forwarding static IP thingy...

I hadn't knowingly changed any settings prior to this problem...it was working fine last month, and then bam, it screwed up

Cheers for the reply, I was beginning to lose hope hehehehe

Actually on the problematic PC. Yeah, on LAN or WIFI Connection, go to the properties of the TCP/IP, and add it there, under IP, Subnet, Gateway.

Of course, make sure you remember your old settings. It should be worth trying both the Routers IP Address, (which should be the default gateway anyway) and loopback address (127.0.0.1). You can actually add both, or one at a time, and leave an old address there.

I just thought that maybe your ISP had problems with it's DNS, or closed it down, ... You can ping the address to find out if it is there at all.

I pinged my ISP's DNS address (I'm not sure if I did it right - I went into CMD, then typed "ping 158.152.1.58") It sent 4 packets, received 4 packets, and lost none. I'm assuming that means everything is alright at my ISP's end.

Currently, my Internet Protocol (TCP/IP) settings are as follows:

IP address: 10.0.0.11 (This is my computer's address as assigned in the router, for port forwarding etc. The other computer connected to the router uses the 10.0.0.8 address).

Subnet mask: 255.0.0.0 (This was set automatically when the other vlaues were set, if I remember correctly)

Default gateway: 10.0.0.2 (This is the router's address)

Below that are the DNS values:

Primary DNS server: 158.152.1.58 (I got this directly from my ISP's info page)

Alternate DNS server: 158.152.1.43 (Same as above)

Like I said, these settings worked fine up until a month ago, when the problems began. They haven't been changed or anything.

Maybe it's a problem with the router itself. I've always had a little bit of trouble setting it up, because I have no idea who manufactured it, and therefore can't find any specific documentation for it (see this thread and this thread). No documentation came with it either, other than instructions on how to turn it on. I'm gonna get a new one at some point - one with a 5,000 page manual! Anyway...

Any ideas?

Thanks for your time mate, much appreciated.

P.S I just checked the other computer in my network, to see if it can flush the DNS. It can, so I guess it's not the router that's casuing the problem. The other computer is set up exactly like mine (except for its IP, which is 10.0.0.8 whereas mine is 10.0.0.11). The only other difference is that I am using Windows XP Professional SP2, and the other PC is using Windows XP Media Centre SP2.

The plot thickens!

I apologies, looks like I have lead you on a merry ride, I should have just searched EE to start with.

Disable the firewall in Xp (done in control panel)
then give it a try,
(ipconfig /flushdns)
if it doesn't work...
. boot to safe mode with network support
. then try your ipconfig /flushdns

That sorted someone else out with the same problem. Hope this helps.

Sorry, David

Hehehe no worries

The Windows Firewall is disabled - I never use it. I booted into Safe Mode (with Network support; it wouldn't let me access the ipconfig function with a minimal "Safe Mode" boot). I received the same error as I do when not in Safe Mode:

"Could not flush the DNS Resolver Cache: Function failed during execution."

I'm just about out of ideas haha. Well, maybe a clean install of the OS, but I'm in no mood for that right now! :p

I use the "Comodo Personal Firewall", if that matters. I don't think it does, because I shut it down, and then tried the DNS flush again, but received the same error. Plus it didn't load in Safe Mode anyway.

Watcha reckon?

EDIT: Could it be my anti-virus software? I use Avast! Anti-Virus. Although I did disable network protection for a while. It didn't help the problem.

I'm starting to think this is a connection problem, apparently rebooting the PC would Flush the DNS anyway.

Is this connected via WiFi. If so, make sure you have WEP Security enabled. If this PC is WiFi, and the other is through a LAN cable, could you try the fault PC using the Working PC connection. If they are both cabled, try swapping cables. If they are both Wifi, try using a Lan cable with the Fault PC.

Could you provide the following information.

If you still have problems, please provide;

Router model - ..................
Working PC Connection - ......................
Fault PC Connection - .....................

I'm sorry I haven't found a good solution so far, but still think it's out there somewhere, Regards, Dave