HI to all..
last week dude didnt accept my password suddenly and didnt work anymore..i couldnt export my backup…i had to uninstall dude on server and installed it again and then i exported backup…after that time,dude dont have any problem but when i restart server ,all of software connect but dude need a lot of time to connect…i get this error:
“NO CONECTION COULD BE MADE BEACUSE THE TA…”…i cant see all of text of error…
has anyone no idea?..i need help:(
This is the same error I had. I posted at http://forum.mikrotik.com/t/dude-3-6-dropping-all-outbound-connections/61836/1 if you wish to follow it.
In my case, that machine is running Dude 3.6 which replaced an install of 2.2 that crashed and I lost all the historical data. So, I formatted it, loaded windows XP, updated it, loaded Comodo Internet Security and allowed appropriate ports through firewall. After running for a day, it would report that error in the bottom left of a remote Dude 3.6 client trying to connect to it. I figured it was the maximum TCP connection limit of XP as per the Event Viewer pointing me in that direction. So, I patched the tcp file to allow 10,000 concurrent tcp connections. It ran ok for a while but had the same thing again a couple days later. Rebooting the machine fixes it until it dies again. Interestingly, I could see currently open tcp connections in Comodo as listing 1000-2000 concurrent connections. When this issue hits, the outbound connections are ZERO. So, by logging into the server I could check for this and see - aha, it needs a reboot. Trying to remotely connect via Dude however, would fail, and yield that error. SO, I rebooted, and increased the polling interval to 60s. Same issue. Increased to 2m… same issue. I still think it is a maximum tcp connection limitation of XP. I seem to recall the Dude 2.2 install I had was set to a 5m poll interval, but it’s gone, so not sure.
Currently, I have the box running and it works till it fails, then has to be rebooted. It has had this behavior about 5 times in 2 weeks.
I am now considering loading a 4.0b3 install on windows 7 Pro versus a linux install via WINE to replace the replacement.
I do however, have a different Dude install… 3.5 I think… sitting on a Linux box. CentOS 5.7 or so. It has been running for over a year fairly reliably with only a few issues. It does not monitor everything though. It’s just for “critical” boxes that need a more rapid notification of ping failures.
I have not yet decided which route I will go. Still looking at both.