I am running RHEL AS 4, I have it authenticating to our ADS server. It works great! I have secure shares setup on it so that i can access them from my windows machines and authenticatiion goes through winbind\ads in the backgroud. But when I want to access a windows share from the linux machine it prompts me for my username/domain/password. I can enter all of the above, well i can even get away with just entering username/password now, and access the share. My question is, how do I access the windows shares with out being prompted for my login info while I am logged into a machine with a domain user account. Sorry if this is confusing, let me know if it is and I will try to reword it.

Other than providing the login credentials within /etc/fstab or a user login script to map the appropriate drives with the corresponding authentication details, I think konqueror is able to handle caching of such credentials after they have been provided the first time, providing the konqueror is not closed. Not sure though, as I've never tried it. I think it's down the OS itself not automatically associating the shares you're accessing the credentials of the current user, which Windows handles automagically when your browse shares, or prompts you if access is denied and so prompting for an additional user account.

Thanks for the reply, that does seem to make sense. The windows shares will probally not be accessed that much from the linux server so it's not to big of a deal. With this server using winbind to authenticate to ADS is great, everthing is almost seemless. This one little inconvenience I can live with.

We have a similar winbind issue for web browsing. Our proxy uses the winbind authentication helpers for Squid, which works great with Windows clients running IE, as it automatically passes authentication details and integrates seamlessly. Non-IE browsers, and thus all Linux workstations, prompt the user the first time a website is requested. Once this is entered, the browsing sessions continues unitl the browser is closed (or 2 hour authentication time limit hit). Doesn't cause much of a problem, and isn't really a workaround as yet. At least the bulk of what you're after is handled quite happily!