hi guys,
i have a strange problem with the dude. when i try to connect remotely from a client, suddenly it reject my authentication… If i restart service or reboot the windows server it working correct…
also when i log on locally on the windows server 2003 where dude is installed and try to login it always reject the 1st authentication and log me in at the second
if anyone knows where the problem is pls help me.
Thanks a lot
p.s. the dude version 3.6 installed as windows service on windows 2003 r2 64bit sp2
I was wondering if you found the resolution, maybe run wireshark and look at the traffic? I don’t have any idea and have not heard of it.
hi Guys, after some analysis i have solved the problem. let me explain:
my dude service is a windows 2003 x64 1,5gb ram (sphere VM) the server is in a domain and have remote desktop enabled.
normally dude open a socket on 2210 tcp and 2211 tcp(both also udp) when a user connect from a remote network with the client all goes well.
here the problem 
when someone go in remote desktop session and open dude directly from the server the dude open a new socket 2210 and 2211 but not close them after exit.
then i had 8 socket from port 2210 and from port 2211. now when i try to establish a connection, i suppose that the client ask to a wrong socket and sometimes got the right one and let me login.
to solve this problem and let my user use remote desktop i have created a remoteapp windows server and i have published dude client as remote app(in a different server) the wherever the user need they can connect to dude via rdpweb as the application is locally installed on the client.
Thanks for support
Giulio