We set Dude to run on a XP server and after Dude loads we can no longer access internet sites.
The server has two NICS - one on the inside of the network and one external.
Any ideas??
Thank you,
Rod
We set Dude to run on a XP server and after Dude loads we can no longer access internet sites.
The server has two NICS - one on the inside of the network and one external.
Any ideas??
Thank you,
Rod
BTW - I’m now running .8 - was running 2.2 before same problem.
Thank you,
Rod
something is wrong with your computer. dude doesn’t interfere with anything. it just pings some devices. are you sure the internet works when dude is closed?
No - Without Dude server running no problem - as soon as Dude server loads - no internet!
Very puzzling.
On machine that has been on the rack for some time handling archive data.
So thats not it!!
Please inform.
Thank you,
Rod
Hello,
Me too. The problems weren’t on a server - just my main XP computer where I first installed TheDude
It’s an amazing thing, by the way. Thank you very much. Free too.. because I work for a charity! ![]()
Whenever I ran TheDude, network connections were really sluggish. Website addresses had to be entered three or four times (I.E. or Firefox) before they appeared.
Using VNC to access computers on the network, I often got the message “unable to connect to host: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. (10055)” This error does not occur with normal use of VNC.
If I kill TheDude service, then all the problems are gone.
But anyhow. The XP computer was unusable with TheDude running, so I am trying a dedicated Dude XP server - which I can access from my main XP computer using a Dude client. That combination seems to work fine so far, with no network errors or problems.
Thanks,
Mark
Very often we had the same. Sometimes our dude machine do not accept new connections. Need to logoff the XP user and then login back to solve the problem and be connected on dude again.
On the machines check your event viewer to see if there is a system warning: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts. I have noticed this happening before with this and another scanning software. I fixed mine by tailoring my scans by the priority of the device - it staggers the traffic and allows me to stay connected.
Try to switch of everything accept ping for any device. Under “Device”, Services"
Than it will work fine.
JWS