Well I downloaded the 4.0 beta software, I think it took me
a whole 15 minutes to install and setup.
Here's a report on how it went.
Equipment
P166 48MB RAM
one 3com nic
one netgear nic
500 MB HD
standard CDROM
standard floppy
Dedicated connection
DNS provided by myip.org
names eserver.myip.org
eserver1.myip.org
IP address 216.162.97.119
Client machines one Linux(SuSe 6.2) and Windows NT
4.0(service pack 4)
Windows networkings
Extremely slow when accessing shares from NT, after I made
the recommended changes for NT locking in the samba docs
browsing of available shares was lightning fast, but when
actually accessing a share my NT box Blue Screened on me.
I'm thinking I could have typed something wrong when adding
and modifing keys in the NT registry so I reversed my
changes and everything works again except for it's still
slow.
I'll check the registry changes again and give you an
update.
I think there is a printing patch, I couldn't find it so can you someone forward it two me. Printing was untested
telnet Access
private net access OK as root
FTP access
With an ibay defined with public access for web and
anonymous ftp, group write and read, group is everyone
(Everyone was defined by me.) I get a message 421 Service
not available. I can however connect as a created user
(sysadmin).
Once connected as a created user I can see my root directory
and home however I can't see any defined ibay's. Two are
defined, eserver1 and eserver2 with internet access.
Virtual Domains (www)
After defining a virtual domain of eserver1.myip.org and
accessing it I get the home page of the primary server.
After looking at at the srm.conf file I noticed that "www"
has been appended to the virtual domain.
I understand that
www.xxxxxx.com is such a common address
that it was put in there to ease use, but maybe when
defining a virtual domain instead of automatically appending
the domain name to "www" you ask for the address of the web
site instead of assuming that all web site domains will have
www proceeding the domain.
The document root in the srm.conf file looks like it's okay,
but I'm used to defining everything under the
directive, I see there is a Document root
defined at the top. Does this directive override the
document root in the directive? After I
changed the template to not include the "www" when looping
through and defining virtual domains I still get the primary
sites index.htm file instead of the one defined in the ibay
for the virtual domain.
Commenting the document root out at the beginning of the
srm.conf template file and just using the parameters in the
directive did solved this problem.
Sorry for the rambling, I'm trying to fix these problems
while I'm writing this.
So my problem was fixed, by removing the "www" and
commenting out the document root at the begining of the
srm.conf template and just letting Apache use the
directive to define the web sites.
By removing the "www" as the default I may have broke the
easy setup when using the manager to setup standard sites.
I'll probably put it back in, I'm just testing it now. I
would like it though if you could ask for the fqdn of the
web site when defining it instead of assuming that all
virtual domains that are defined will include www as part of
the address.
Virtual Domains (email)
I'm not familiar with qmail, but my problem is that when
using virtual domains and checking mail from OE 5 I get all
of the mail for the user regardless of what virtual domain
the client software was directed to check. So if I define
domain eserver1 and domain eserver on the box and create a
user, when I check email from OE I'll receive email from
both eserver1 and eserver even when the mail is addressed to
useraccount@eserver.myip.org. Anyway to change this to only
receive mail from the virtual domain that is defined in the
client software?
I'll post more when I have more time for testing.
Carl
1 Replies
842 Views