Cannot run .EXE after joining domain

I am running into a problem when setting up a W2003 server as Terminal Server
for three remote users in another building.

This is a very small network:

Server 1: Windows 2003 Server, Domain Controller (primary), SQL Server, File
Server
Server 2: Windows 2003 Server, Terminal Server

Server 1 runs a Financial System requiring SQL Server. The setup files
reside on a directory on Server 1. I can run Setup.exe from Server2 when it
is not a member of the domain, but once I join the domain every user,
including administrators, receives the error message "access denied... not
enough permissions". I ran Setup.exe from my laptop after joining the domain,
using the same account that failed on Server2 after it joined the domain.

I suspect an automatic security policy is preventing running executables but
do not know where to look.

Any help appreciated.

Hello EHuggz,

Check the permissions on the directory where setup files are make sure sure
admin have full control. Are these apps running trough Group policy?

--
Isaac Oben [MCTIP:EA, MCSE]
"EHuggz" <EHuggz@discussions.microsoft.com> wrote in message
news:5F1C18D7-D5AB-46EC-B308-9C8D5D321733@microsoft.com...
>I am running into a problem when setting up a W2003 server as Terminal
>Server
> for three remote users in another building.
>
> This is a very small network:
>
> Server 1: Windows 2003 Server, Domain Controller (primary), SQL Server,
> File
> Server
> Server 2: Windows 2003 Server, Terminal Server
>
> Server 1 runs a Financial System requiring SQL Server. The setup files
> reside on a directory on Server 1. I can run Setup.exe from Server2 when
> it
> is not a member of the domain, but once I join the domain every user,
> including administrators, receives the error message "access denied... not
> enough permissions". I ran Setup.exe from my laptop after joining the
> domain,
> using the same account that failed on Server2 after it joined the domain.
>
> I suspect an automatic security policy is preventing running executables
> but
> do not know where to look.
>
> Any help appreciated.

I stumbled on the answer this afternoon. IE was blocking access to the files,
presumably because file access was in FQDN format. Listing the two local file
servers in the Local Internet Zone solved the problem. Now I just have to
figure out how to make IE aware on Server2 so I don't have to setup each
users IE configuration individually.

The real issue was that the error message made no reference to IE. It wasn't
until I removed the server from AD and was trying several ideas to solve the
problem that I noticed I could not access any files from either server when
using FQDN, but could run Setup.exe from the C:\Drive. I then noticed that
when running the file as a group member server rather than AD server, I
received a message asking if it was OK to run Setup.exe. I pressed Help and
received an IE help screen - which eventually lead me to test various
security settings in IE and resolve the problem.

Very, very frustrating - but now resolved.

"Isaac Oben [MCITP,MCSE]" wrote:

> Hello EHuggz,
>
> Check the permissions on the directory where setup files are make sure sure
> admin have full control. Are these apps running trough Group policy?
>
> --
> Isaac Oben [MCTIP:EA, MCSE]
> "EHuggz" <EHuggz@discussions.microsoft.com> wrote in message
> news:5F1C18D7-D5AB-46EC-B308-9C8D5D321733@microsoft.com...
> >I am running into a problem when setting up a W2003 server as Terminal
> >Server
> > for three remote users in another building.
> >
> > This is a very small network:
> >
> > Server 1: Windows 2003 Server, Domain Controller (primary), SQL Server,
> > File
> > Server
> > Server 2: Windows 2003 Server, Terminal Server
> >
> > Server 1 runs a Financial System requiring SQL Server. The setup files
> > reside on a directory on Server 1. I can run Setup.exe from Server2 when
> > it
> > is not a member of the domain, but once I join the domain every user,
> > including administrators, receives the error message "access denied... not
> > enough permissions". I ran Setup.exe from my laptop after joining the
> > domain,
> > using the same account that failed on Server2 after it joined the domain.
> >
> > I suspect an automatic security policy is preventing running executables
> > but
> > do not know where to look.
> >
> > Any help appreciated.
>

You might want to refer to http://support.microsoft.com/kb/815141 and
http://msdn.microsoft.com/en-us/libr...81(VS.85).aspx for additional
information regarding this subject...

hth
Marcin

"EHuggz" <EHuggz@discussions.microsoft.com> wrote in message
news:382E7A41-8679-4C91-8718-D2868CB99ABA@microsoft.com...
>I stumbled on the answer this afternoon. IE was blocking access to the
>files,
> presumably because file access was in FQDN format. Listing the two local
> file
> servers in the Local Internet Zone solved the problem. Now I just have to
> figure out how to make IE aware on Server2 so I don't have to setup each
> users IE configuration individually.
>
> The real issue was that the error message made no reference to IE. It
> wasn't
> until I removed the server from AD and was trying several ideas to solve
> the
> problem that I noticed I could not access any files from either server
> when
> using FQDN, but could run Setup.exe from the C:\Drive. I then noticed that
> when running the file as a group member server rather than AD server, I
> received a message asking if it was OK to run Setup.exe. I pressed Help
> and
> received an IE help screen - which eventually lead me to test various
> security settings in IE and resolve the problem.
>
> Very, very frustrating - but now resolved.
>
> "Isaac Oben [MCITP,MCSE]" wrote:
>
>> Hello EHuggz,
>>
>> Check the permissions on the directory where setup files are make sure
>> sure
>> admin have full control. Are these apps running trough Group policy?
>>
>> --
>> Isaac Oben [MCTIP:EA, MCSE]
>> "EHuggz" <EHuggz@discussions.microsoft.com> wrote in message
>> news:5F1C18D7-D5AB-46EC-B308-9C8D5D321733@microsoft.com...
>> >I am running into a problem when setting up a W2003 server as Terminal
>> >Server
>> > for three remote users in another building.
>> >
>> > This is a very small network:
>> >
>> > Server 1: Windows 2003 Server, Domain Controller (primary), SQL Server,
>> > File
>> > Server
>> > Server 2: Windows 2003 Server, Terminal Server
>> >
>> > Server 1 runs a Financial System requiring SQL Server. The setup files
>> > reside on a directory on Server 1. I can run Setup.exe from Server2
>> > when
>> > it
>> > is not a member of the domain, but once I join the domain every user,
>> > including administrators, receives the error message "access denied...
>> > not
>> > enough permissions". I ran Setup.exe from my laptop after joining the
>> > domain,
>> > using the same account that failed on Server2 after it joined the
>> > domain.
>> >
>> > I suspect an automatic security policy is preventing running
>> > executables
>> > but
>> > do not know where to look.
>> >
>> > Any help appreciated.
>>