Frank: Always appreciate your expertise! Yes, this all started after one of the XP automatic updates.
I had both Framework 1.1 and 2.0 Configuration on my list. I chose 2.0. I had options of Manage the assembly cache, manage configured assemblies, configure code access security policy, adjust remoting services, manage individual applications. I picked "configure code access security policy" because that seemed close. I clicked on "runtime security" on the left, then Actions / Adjust Security. Chose the machine, Local Intranet, Full Trust. Also changed Trusted Sites to Full Trust. Rebooted, same darn thing... As for your last paragraph, everyone on the domain is having the same problem. It's kinda embarrassing that RBase is the only "non-trusted" site. Part of the larger M$ plan, I guess.... Karen > Sorry I have been away from the list for a while with other projects. I > suspect the update on your XP machine updated the Microsoft .Net Framework. > In this there is a whole section on trusted sites locally and on the > Internet that you can set per user or per machine. I would start here by > going > to the following > > Start-Control Panel - Administrative Tools - Microsoft .Net Framework (1.1 > or 2.0) Click on that and then click on adjust .Net security > > Again you can do this for just a certain user or for the entire machine (I > would start with the machine). Then I would go under Local Intranet and > change the setting to FULL TRUST. I would also adjust the trusted sites to > Full Trust, then go into your trusted sites and add that server as a > trusted site. > > The only other area I can think of that might be giving you a problem is > in either the Local GPO or Domain GPO, a network person with domain admin > permissions would need to make a change if it is a GPO issue, but if no one > else in the domain is having an issue I find this unlikely to be the > culprit. >
