home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Media Portal freezes on wake
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="HTPCSourcer" data-source="post: 1161127" data-attributes="member: 74879"><p><em>Some</em> new findings: After manually <u>hibernating</u> the PC yesterday, it came up with the usual partial home screen on top of the Windows desktop, and stayed like this, yet did not crash. So removing the Info plugin did make an effect.</p><p></p><p>However, I found out that the server shares were not accessible, hence no wonder that MP is unresponsive because databases are remote on the server. The attempt to manually access the share (e.g. in Explorer via \\server) throwed an error message that this user was not allowed. As the PC is part of a domain, user acount names have the format domain/username. I suspect that after resume from hibernate something is going wrong with the autologon communication and only the username part got transmitted to the server.</p><p></p><p>Instead of entering the credentials directly into the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon), I now used netplwiz to create entries from the user selection and password dialogues. And surprise, the data are different. <em>DefaultDomainName</em> now contains the name of the PC (!) whereas <em>DefaultUserName</em> is now domain\HTPC1. So it appears that for a year I have been working with the incorrect assumption that DefaultDomainName does what the name insinuates and stores the name of the associated domain - well it does not.</p></blockquote><p></p>
[QUOTE="HTPCSourcer, post: 1161127, member: 74879"] [I]Some[/I] new findings: After manually [U]hibernating[/U] the PC yesterday, it came up with the usual partial home screen on top of the Windows desktop, and stayed like this, yet did not crash. So removing the Info plugin did make an effect. However, I found out that the server shares were not accessible, hence no wonder that MP is unresponsive because databases are remote on the server. The attempt to manually access the share (e.g. in Explorer via \\server) throwed an error message that this user was not allowed. As the PC is part of a domain, user acount names have the format domain/username. I suspect that after resume from hibernate something is going wrong with the autologon communication and only the username part got transmitted to the server. Instead of entering the credentials directly into the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon), I now used netplwiz to create entries from the user selection and password dialogues. And surprise, the data are different. [I]DefaultDomainName[/I] now contains the name of the PC (!) whereas [I]DefaultUserName[/I] is now domain\HTPC1. So it appears that for a year I have been working with the incorrect assumption that DefaultDomainName does what the name insinuates and stores the name of the associated domain - well it does not. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Media Portal freezes on wake
Contact us
RSS
Top
Bottom