Koozali.org: home of the SME Server

behaving like PRIVATE Server

Phil Gartner

behaving like PRIVATE Server
« on: January 06, 2002, 05:11:04 AM »
ANyone shed some light on this please.

I have a server set up using dialup and Dyndns, that behaves like a Private server in that HTTP and MAIL cannot be seen externally but everything works internally.

Internal network 192.168.0.x Mask 255.255.255.0

External - Supplied by ISP

Gateway is set to 192.168.65.1  ???? This doesn't make sense to me.

I can FTP to the server externally.
I can send mail out, but not receive.

Cheers
Phil

Judy Morgann

Re: behaving like PRIVATE Server
« Reply #1 on: January 07, 2002, 08:14:03 PM »
Hi,
problem seems to be that your server doesn´t accept mail from outside. look at the logfiles. first you need a mx record for your domain name so that the senders mailserver knows who is responsible for the mail <- your server - i think dyndns.org does it automatically or you have to switch it on on their website.
then you have to configure your server that he accepts mail for your domainname. just give your e-smith server the domainname of your dyndns.org subdomain. you can add a virtual domain in the e-smith webmanager <- your dyndns.org subdomain. eg. your-server.dyndns.org.

hope this helps if not ask again with more details (error message in your logfiles...)

greetings
judy

Mike Daley

Re: behaving like PRIVATE Server
« Reply #2 on: January 08, 2002, 12:47:07 AM »
Judy et al:

I don't think that will do it.  I've had the same problem.  Even if I (outside my network) use my IP address the server won't respond to http, ftp or even ssh connections.  I'm running 5.1b3.  At the moment I've reverted back to 4.1.2 until I can resolve this issue.

Any more help you may be able to offer would be very much appreciated.

Cheers,
Mike

RypPn

Re: behaving like PRIVATE Server
« Reply #3 on: January 19, 2002, 01:38:05 AM »
I noticed exactly the same problem you describe on installing v5b4, but this does not seem to be an sme issue. Rather I believe the MX records may not be configured correctly by your dyn/dns/go resolver (as hinted at by Julie).

My workaround/solution was kinda basic, but it works for me...

I set my domain to the the same as my isp e-mail address e.g. for Phil I would use optusnet.com.au as the domain (reason - at least you can be sure their mx records are correct). All my dyndns domains are virtual, set up on I-Bays, and guess what...

I receive mail no problems, users created on the sme box (and recognised by my ISP as e-mail users) automagically receive mail and holds them until my winblows clients lift them from the qmail server. One tip I will give is that if you wish to use IMP to retrieve mail via the web, set the mail accounts in your winblows clients to IMAP or the IMP inbox will always be empty if a pop client gets there first :)

Hope this is not off-topic and it helps a little.

Best Regards,
                       RypPn


P.S. MP3 Jukebox r0c|