Timeout when pulsing

[Bleeve]

2 days ago my WhatPulse started to timeout whenever it tried to pulse. The error message I get is

"Error: Could not connect to server."

I have never experienced this before and now I get it every time. As far as I know, I have made no changes which should be able to affect this. I'm on Vista x64.

*EDIT* I just noticed there are other posts about this (for some reason I couldn't see them when I looked before I posted...), my apologies.

[JetSet]

Checking through the user stats I see that lots of pulses are being recorded but I'm getting the same error as you. I suspect that the interface between version 1.5 and the server is broken. I'm sure it'll get fixed soon


Pete

[theHacker]

Version 1.5 pulses the results to the server 83.96.159.250:3490 which is down for 2 days by now. But the server at 83.96.159.249:3490 which the client 1.6 is using is fully operational.

Use this trick to be able to pulse with 1.5:
Open [FONT="Lucida Console"]%SystemRoot%\system32\drivers\etc\hosts[/FONT] with your editor and append the line

Code:

83.96.159.249 whatpulse.org

. Afterwards flush your DNS cache by opening a terminal (start menu / run: [FONT="Lucida Console"]cmd[/FONT]) and type the command

Code:

[FONT="Lucida Console"]ipconfig /flushdns[/FONT]

Be aware: This will redirect the host whatpulse.org, so you will not be able to open the WhatPulse website under http://www.whatpulse.org/ (forums should work - I think).
If you want to undo this, simple delete the inserted line in the hosts file and flush the DNS cache again.

[Webbax]

theHacker Wrote:Version 1.5 pulses the results to the server 83.96.159.250:3490 which is down for 2 days by now. But the server at 83.96.159.249:3490 which the client 1.6 is using is fully operational.

Use this trick to be able to pulse with 1.5:
Open [FONT="Lucida Console"]%SystemRoot%\system32\drivers\etc\hosts[/FONT] with your editor and append the line

Code:

83.96.159.249 whatpulse.org

. Afterwards flush your DNS cache by opening a terminal (start menu / run: [FONT="Lucida Console"]cmd[/FONT]) and type the command

Code:

[FONT="Lucida Console"]ipconfig /flushdns[/FONT]

They should put in both servers so it could work allways. Only a tip...

[Mirre]

Tnx for the tip TheHacker. I was able to pulse now because of your tip!
You've made my day

[Opt!k]

I have the same problem and I'm using version 1.5.1 (Cherry) too. I tried to pulse on an other computer so I tried to do it like it's told in knowledge base "using whatpulse on an USB drive". Then I noticed that this just works for versions 1.6 and higher.

Then I tried it the way it is mentioned here and now I keep getting the error: "Acitivity throttle breached, try again in an hours or so". I googled this error but I didn't find any helpful threads. Will it really work if I wait?

[Mirre]

You get this "Acitivity throttle breached, try again in an hours or so" error when you tried to pulse to often. You should be able to pulse in a couple of hours.

[Webbax]

Opt!k Wrote:I have the same problem and I'm using version 1.5.1 (Cherry) too. I tried to pulse on an other computer so I tried to do it like it's told in knowledge base "using whatpulse on an USB drive". Then I noticed that this just works for versions 1.6 and higher.

Then I tried it the way it is mentioned here and now I keep getting the error: "Acitivity throttle breached, try again in an hours or so". I googled this error but I didn't find any helpful threads. Will it really work if I wait?

Im also using 1.5.1 Cherry and it works with that tip theHacker gave us

[smitmartijn]

Hi,

Disregard that hosts file edit. It should work again.

[JetSet]

Yep, pulsing again

Pete