From: David Cannings <lists@edeca.net>
To: netfilter@lists.netfilter.org
Subject: Re: mail server acces pb
Date: Thu, 22 Apr 2004 23:31:14 +0100 [thread overview]
Message-ID: <200404222331.14497.lists@edeca.net> (raw)
In-Reply-To: <HWLF8W$9F9583659D96FB958291928238874B93@tiscali.fr>
On Thursday 22 April 2004 23:17, kmc@tiscali.fr wrote:
> i have a 2 machines network in workgroup. One LINUX connected to
> INTERNET through ADSL AND A LAPTOP/XP that can't access to my ISP mail
> server with message: "can't find pop server's name pop.libertysurf.fr"
> and then
> "your mail server closed the connection
From looking at your rules I do not see anything that would stop your
Windows machine from accessing the Internet however I would check the
following:
1) Can your Windows machine resolve the hostname for pop.libertysurf.fr?
A good way to check would be to pull up a command line (Start->Run->"cmd"
worked in 2000 and most likely will in XP too) and use the tool
"nslookup". `nslookup pop.libertysurf.fr` should show you.
2) Does your Windows machine access anything else as expected? For
example, can you web surf or use other Internet applications?
3) If no to 2 above, are your DNS settings in Windows correct? I cannot
say what they should be as I do not know who your ISP is but if your
Linux machine works fine, use the same entry as in /etc/resolv.conf.
I would also note that having a default ACCEPT policy can be a bad thing.
To satisfy the paranoid a default DENY policy with rules crafted inside
to let only what you want through is the safest way to build your
firewall. One other note is that based on your ruleset, I have made the
presumption that the Linux machine is acting as the gateway.
David
prev parent reply other threads:[~2004-04-22 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 22:17 mail server acces pb kmc
2004-04-22 22:31 ` David Cannings [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200404222331.14497.lists@edeca.net \
--to=lists@edeca.net \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.