Vista - Launcher Connect problems - One solution

[Zor_Prime]

I've seen people having this problem and I know it's one of those things that Turbine has started looking into recently.

I just built a new system and installed Vista then installed DDO from the original disks. Upon running the launch, I got the red "X" next to "Connect" and a constant retry. I was not able to get to the long 12K files update. The solution was to give "Full Control" to "Authenticated Users" for dndlauncher.exe and dndclient.exe (note: The launcher may have been good enough...I simply did both before trying).

Details:

- Vista Home Premium (legit)
- Administrator Account only (no other account on the system)
- Firewall turned off
- Malware protection turned off
- User Control turned off
- Defender turned off
- Internet Security to default - medium

Instructions:

NOTE: Try at your own risk. This worked fine for me.

1. Right-Click dndlauncher.exe from the "\Turbine\Dungeons & Dragons Online - Stormreach" directory.
2. Select "Properties"
3. Select the "Security" tab from the resulting Window.
4. Note the list box containing various access levels. The title of this list box (not the whole window) may be something like "Permissions for Authenticated Users". It could be different for you but I haven't played with it enough to know. Nonetheless, if the "Full Control" is not checked in this box, then you need to get it checked.
5. Click the "Advanced" button below the Permissions list box. The "Advanced Security Settings" dialog should result.
6. In the "Advanced Security Settings" dialog, click the "Edit" button in the lower left and this will result in *another* "Advanced Security Settings" dialog.
7. In this dialog, you should see a Name with a Permission of "modify" (in my case, it was "Authenticated Users"...only one Name should have this permission).
8. Select the Name with the "modify" Permission and click the "Edit" button. This will result in the "Permission Entry for dndlauncher.exe" dialog.
9. In this dialog, check the "Full Control" check-box then click "OK".
10. This will return to the previous dialog and you should now see the Name with a "Full Control" permission and "<not inherited>" in the "Inherited From" column.
11. Ok out of everything and then repeat for dndclient.exe.


Again, this was a fresh Vista install with nothing on the system other than the relevant device drivers and Firefox. I had a single Admin account and just about every security setting turned off (this was by choice not because of this problem). You may not need to turn off every security setting for this to work.

Also, please note that I've done no research into this problem (if it is a problem at all). I just built the system and was trying to hurry up and install everything...I want to get in game fast. If someone finds a quicker way or discovers that you don't have to edit both .EXE files, or whatever, then by all means, let me and everyone else know.



/I started this message at about 750...I'm not even to 4000.

[Ilara]

I did exactly what you said in your post, but it is still saying that I cannot be an administrator! Help!

[EazyWeazy]

Vista and DDO are definitely goofy. You can try right clicking the executable and use the 'run as administrator' option. You may also try creating a second user account on the computer that does not have admin rights by default and using that account for the initial updates. The only way I can get Vista to update Risia is through this method.

I wish I'd kept notes on what I did to work around this as I had the same issues when I installed on Vista, but I just don't remember the exact steps. Sorry.

[jkm]

I did exactly what you said in your post, but it is still saying that I cannot be an administrator! Help!

by default, if this is the main account on your home pc it is an administrator account. it gets a little tricky when you are using a work computer with different policies (especially ones where you aren't the admin)

click control panel -> user accounts -> manage user accounts (requires admin) and put yourself in the administrator group