Guest EHuggz Posted March 12, 2009 Posted March 12, 2009 I am setting up a W2003 Server as a Terminal Server that accesses a financial system on another file server. Everything works fine as long as the W2003/TS is not a member of the domain, but after joining the domain I can no longer run the executable on the file server required to setup users on TS - receiving a "do not have required permissions" error. Removing the server from the domain restores the ability to run the .EXE setup file. This is a very small network with just two servers. Server 1: 2003 File Server, SQL Server, and domain controller (primary). Server 2: 2003 Server and Terminal Server. The TS is used by users in a remote building who need access to the Financial App. I connected my laptop to the domain and was able to run the executable using the same domain account as the one that did not work when the 2003/TS server was added to the domain. I suspect some type of Security Policy is preventing executable access. Any help appreciated. Quote
Guest Peter Foldes Posted March 13, 2009 Posted March 13, 2009 EHuggz This is not the server.security. newsgroup Post it here On the web: http://www.microsoft.com/communities/newsg...server.security -- Peter Please Reply to Newsgroup for the benefit of others Requests for assistance by email can not and will not be acknowledged. "EHuggz" <EHuggz@discussions.microsoft.com> wrote in message news:6BAE3D24-49C4-4299-94FE-80C648293FB7@microsoft.com...<span style="color:blue"> >I am setting up a W2003 Server as a Terminal Server that accesses a financial > system on another file server. Everything works fine as long as the W2003/TS > is not a member of the domain, but after joining the domain I can no longer > run the executable on the file server required to setup users on TS - > receiving a "do not have required permissions" error. Removing the server > from the domain restores the ability to run the .EXE setup file. > > This is a very small network with just two servers. > > Server 1: 2003 File Server, SQL Server, and domain controller (primary). > Server 2: 2003 Server and Terminal Server. > > The TS is used by users in a remote building who need access to the > Financial App. > > I connected my laptop to the domain and was able to run the executable using > the same domain account as the one that did not work when the 2003/TS server > was added to the domain. I suspect some type of Security Policy is preventing > executable access. > > Any help appreciated. </span> Quote
Guest EHuggz Posted March 13, 2009 Posted March 13, 2009 Peter, It wasn't clear this problem was a security, and I was not sure where to post. As a result I posted my issue on several forums. It turns out the problem was related to Windows 2003 IE settings which prevent executing off host executables by default - even if not accessing the program via IE. Tracking down the issue was made more difficult because because the error mention made no mention the error was generated due to settings in IE. I appreciate your taking the time to point me in a better direction, and apologize for the multiple posts. "Peter Foldes" wrote: <span style="color:blue"> > EHuggz > > This is not the server.security. newsgroup > > Post it here > > On the web: > http://www.microsoft.com/communities/newsg...server.security > > -- > Peter > > Please Reply to Newsgroup for the benefit of others > Requests for assistance by email can not and will not be acknowledged. > > "EHuggz" <EHuggz@discussions.microsoft.com> wrote in message > news:6BAE3D24-49C4-4299-94FE-80C648293FB7@microsoft.com...<span style="color:green"> > >I am setting up a W2003 Server as a Terminal Server that accesses a financial > > system on another file server. Everything works fine as long as the W2003/TS > > is not a member of the domain, but after joining the domain I can no longer > > run the executable on the file server required to setup users on TS - > > receiving a "do not have required permissions" error. Removing the server > > from the domain restores the ability to run the .EXE setup file. > > > > This is a very small network with just two servers. > > > > Server 1: 2003 File Server, SQL Server, and domain controller (primary). > > Server 2: 2003 Server and Terminal Server. > > > > The TS is used by users in a remote building who need access to the > > Financial App. > > > > I connected my laptop to the domain and was able to run the executable using > > the same domain account as the one that did not work when the 2003/TS server > > was added to the domain. I suspect some type of Security Policy is preventing > > executable access. > > > > Any help appreciated. </span> > > </span> Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.