Hello
I have tried everything (I guess) to make dude work on windows7 but have not been successful.
I tried the stable version and beta as well, run them as administrator, run with compatibility mode for WindowsXp, installed them as administrator,
but dude fails to discover the network. In all the cases, it installs correctly, connects to the local host, but when I try to do discover it can not find my network.
The bar at the bottom that shows the progress goes up to 50% and then stops.
I tried a virtual machine with windowsXP on the same PC and it works there. The virtual WindowsXP was already there for testing purpose,
I will try latter with a virtual Windows7.
So, the problem lies between dude and windows7. Any idea?
This is funny, one never stops to get surprised by software behavior.
I tried now again dude beta, run it as administrator, and tried to connect to the local server,
but the password was wrong. I was surprised, moments ago I connected successfully. So, I tried
with the default login, and it connects now, and it discovers as well!! Go figure.
I will try a restart of the PC to see what is going on. Maybe running it from the virtualXP did something
to the host machine?
Again me
Restarted the PC, started dude and … no discover. Drives me crazy, am I getting old? What is going on?
So, decided to uninstall. The uninstall can not stop the dude server by itself, I have to do it manually using
the task manager of windows. After that the uninstall is successful.
Installed again resetting the old configuration, started again dude and now discovery works.
Restarted PC, started dude once more and looks fine, so far.
I guess my OS is corrupted somehow by the many tests done on this PC, the only reason I can think of
such strange behavior. Any way, until now looks okay.
No, I didn’t. But right now it is working fine. Pretty strange anyway.
I guess there must have been some old installation left over, or somehow windows is corrupted.
Right now, the beta version is working good. If anything strange happens again, I will keep you posted.
I have the same problem as described in the first post. Dude’s Network Discovery doesn’t work on Windows 7.
I can’t make the dude work. So I installed the dude service on Virtual WinXP and it works fine. I can connect to the service with client installed on win7.
If you have solved the problem please let us know.
im using dude on windows 7 proffesional x64 and it is runnig fine. What you need to do to always run dude as administrator, because if you do not do that sometimes you could see local problem when trying to ping. Also if you at first time run dude in non administrator mode and discover your network after you close it and run it as administrator you will have to scan your network again. i dont know why the scanned network disapears when you run dude in admisnitrator mode
@kauk, it’s not they I have solved the problem. It just started working. As I said in my first post
I tried it install as admin, run it as admin, run in comparability mode, run both as admin and compatibility mode,
and yet it wouldn’t discover. The process of discovering stopped at the stage of finishing the network.
I tried it on another PC which runs windows7 on the same network, and it gave the same problems.
So, I don’t know where to point the finger for such behavior. Unfortunately I didn’t found anything in the log
of dude, it would have been nice to see something in the log.
Caci99, there are 2 things you have to do… first one, turn off UAC. Next, go into a control panel => administrative tools => services. Find secondary logon, stop service and set it to disabled. Second one solves a trouble with a need to use different administrative rights. Only problem I had is a need to change value localhost to 127.0.0.1.
I am running Dude V4.0 beta 3 on Windows 7 64-bit with Kaspersky Internet Security 2013 without any major problems.
@mves, thank you. But anyway it is working fine right now. I have installed dude as a service as well, and it runs okay. I didn’t even needed to disable UAC. So far so good
