[Zope] Zope has encountered an error while publishing this re source

Rengasamy, Samy srengasamy@firstam.com
Wed, 27 Mar 2002 21:03:07 -0600


I have found the following differences.
I am not sure if that would make a difference.

I was able to manage zope at the physical location.

Following are the entries in Z2.log, when I try to manage remotely:
*****************
remote-ip - admin [27/Mar/2002:20:55:52 -0500] "GET /manage_main HTTP/1.1"
200 22459 "http://zope-ip:8080/manage" "Mozilla/4.0 (compatible; MSIE 5.01;
Windows NT)"

remote-ip - Anonymous [27/Mar/2002:20:55:52 -0500] "GET /p_/sp HTTP/1.1" 200
300 "http://zope-ip/manage_main" "Mozilla/4.0 (compatible; MSIE 5.01;
Windows NT)"
*****************

Following are the entries in Z2.log, when I try to manage locally:
*****************
local-ip - admin [27/Mar/2002:20:19:28 -0500] "GET /manage_main HTTP/1.1"
200 22459 "http://local-ip:8080/manage" "Mozilla/4.0 (compatible; MSIE 5.0;
Windows NT; DigExt)"
local-ip - admin [27/Mar/2002:20:19:28 -0500] "GET /p_/sp HTTP/1.1" 200 300
"http://local-ip:8080/manage_main" "Mozilla/4.0 (compatible; MSIE 5.0;
Windows NT; DigExt)"
*****************

When I try to log remotely the id stays 'Anonymous' for some reason.
Also I do not know if the browser version makes any difference?

For intranet access, I have the lowest security setup at IE options.

I am completely clueless here....


Thanks,

Samy Rengasamy.

-----Original Message-----
From: Mike Renfro [mailto:renfro@tntech.edu]
Sent: Wednesday, March 27, 2002 8:03 PM
To: Rengasamy, Samy
Cc: 'Mike Renfro'; 'zope@zope.org'
Subject: Re: [Zope] Zope has encountered an error while publishing this
re source


On Wed, Mar 27, 2002 at 07:49:45PM -0600, Rengasamy, Samy wrote:

> I am trying to manage zope remotely over the intranet.  Should I be
> logging on at the physical location?

Shouldn't matter, unless you've done something odd with your
security. I manage all my sites remotely, and as soon as I made my
user with a Owner and Manager role, it all worked. Might have had to
close and restart the browser, but nothing more drastic than that. I
got the solution off an IRC log I found on Google.

-- 
Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
931 372-3601 / Tennessee Technological University -- renfro@tntech.edu