Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Tyrone Miles on January 26, 2003, 02:04:18 PM
-
http://servername/server-resources/
Is this something new in 5.6 and does it work. On the page for new release it says you can go to this on your server to get the winodws XP patches.
This doesn't work on my server.
-
try \servername_or_IP\server-resources
i.e - windows networking
-
Doesn't work. And it's written in the documentation as: "This patch is made available via the web server, via the URL "http://servername/server-resources/".
Thanks.
-
What is the name of your e-smith box? Where it says servername place that name in the url above.
-
Come on I am not a pro but I do know that I must put the host name or IP where it says servername. LOL!
This is an upgrade from 5.5 to 5.6 maybe that is the problem?
-
question are you getting page can not be displayed or a 403 of 404 or 503 or 500 errors in the web Browser
if so try https://server-name/server-resources
-
Same problem here:
403: You don't have permission to access /server-resources/ on this server.
Either with http and https
-
Yea that is the same thing I got Thor. :-(
-
well using putty, i found the files in:
/home/e-smith/files/server-resources/regedit
win98pwdcache.reg
winxplogon.reg
try if calling the file directly work
http://servername/server-resources/winxplogon.reg
jochen
-
I see the files there but I can not access them from a browser. :(
-
Same here, I'm getting 404's on all combinations.
-
I just reviewed the httpd.conf on my sme. the alias entry is set to
/home/e-smith/files/server-resources/
the ownership for dirs down to regedit is 755 root.root
the files are 644 root.root.
so as apache runs as www.www it is allowed to read this
try if calling the file directly work
http://servername/server-resources/regedit/winxplogon.reg
if not try to chown dir /server-resources/ and everything below it
to www.www
jochen
it's 05:11am here, so I'm off to work now
-
I have sent the following bug report to bugs@e-smith.com
Fault: Accessing http://servername/server-resources/ results in a 403 browser error with the following error message in httpd error logs
[Mon Jan 27 23:31:55 2003] [error] [client 192.168.2.65] Directory index forbidden by rule: /home/e-smith/files/server-resources/
Resolution:
Modify /etc/e-smith/templates/etc/httpd/conf/httpd.conf/ 85ServerResourcesAccess from
# Server resources access configuration
order deny,allow
deny from all
{
$OUT .= " allow from $localAccess\n";
}
to include Options Indexes
# Server resources access configuration
Options Indexes
order deny,allow
deny from all
{
$OUT .= " allow from $localAccess\n";
}
Cheers,
Jon Blakely
-
Jon & Tyrone, Have you filed this as a bug report with the solution that you have?
-
Craig wrote:
>
> Jon & Tyrone, Have you filed this as a bug report with the
> solution that you have?
Jon Blakely wrote:
>
> I have sent the following bug report to bugs@e-smith.com
-
Sorry about that, must have missed it.
Next time I'll read things twice.
Bill Talcott wrote:
>
> Craig wrote:
> >
> > Jon & Tyrone, Have you filed this as a bug report with the
> > solution that you have?
>
> Jon Blakely wrote:
> >
> > I have sent the following bug report to bugs@e-smith.com
-
Try with the trailing '/'
hence:
http://servername_or_IP/server-resources/
vice
http://servername_or_IP/server resources
-John-
-
Does not work here
-
What IP does your "servername" resolve to?? The internal IP or the external IP.?? This URL is set to work on the internal LAN only. For example,
http://63.224.194.225/server-resources/
does not work as it is my testbox's external IP.
http://192.168.0.20/server-resources/
does work as it is my internal IP.
I get this same result when trying to access the server-manager on my testbox (i.e., my testbox domain resolves to the external IP).
You will only see this on SME boxes other than the one that is serving DNS requests as SME is not set with DDNS capabilities
Greg
-
It resolves my local IP, but I didn't use the name anyway (ie. I tried to connect IP-based)
-
mine say You are not authorized to view this page.
-
We foudn that out already Gregg...as mentioned before.
-
Did you perform a post-upgrade AFTER you changed the template
(/sbin/e-smith/signal-event post-upgrade)
Vinnie