Jpoandl:
Thanks for the message!
A little background... I have written an ASP.NET application targeted at Internet Explorer which serves as general business management software for a company with several locations. Up until recently, the application was hosted on an XP desktop, but the IIS user throttling, security concerns, and my eternal love for HTTP compression dictated we upgrade to a server OS. I installed a small business server 2003. Now, in the main location, there is a domain with the SBS and 2 client computers. Several remote locations access the management software over HTTPS, too, but they are irrelevant to this problem.
The problem is that the client wants to be able to use the server in a limited fashion solely for this application. It is their attempt to save the $1000 or so dollar expense of putting in an additional computer just to use internet explorer.
In order to facilitate this, I went to
Under "Default Domain Controller Security Settings - > User Rights Assignment -> Allow Log On Locally"
Under "Default Domain Controller Security Settings - > User Rights Assignment -> Allow Log On Through Terminal Services"
and added the "Users" group. I did this with the Terminal Services also as a test. I discovered that both Terminal Services and local logon have the same problem, FYI.
The problem is, whenever a JavaScript "window.open" is used in my Internet Explorer based application it does not open. The popup windows are called in an onclick event of button elements, but nothing happens. This issue only occurs on the SBS, not on the XP Pro computers in the network.
Also, any Internet explorer feature which would open another window does not work. For instance, "View Source," and "Find On This Page" both do nothing.
I have turned off "Enhanced Security" for both users and administrators in the SBS "Add/Remove" section.
I have added the applications home address as an "Intranet" site on all computers and all users.
I have lowered the "Intranet" security options to the minimal levels on all computers and all users.
None of this makes a difference.
I also have been testing this problem on the rest of the internet to see what other odd behavior would come up. In many, many places I get "Library Not Registered" errors. For instance,
generates one on this line:
if (!hp.isHomePage('
{document.write("<p><a href=\"/mgyhp.html\" onClick=\"style.behavior='url(#default#homepage)';setHomePage('
Google Your Homepage!</a>");}
Obviously this is some kind of a security setting on the server, but I can't find it identified anywhere in the documentation. I have turned off all of the security "features" I know about...