Hi Shaggy. Let's focus on the Linux part, since this is after all a Linux
list. (anyway, it sounds like your Win95 mail problem was just the need to
reconfigure the host properly as standalone.)
Just to be sure: you CAN run a telnet session and a Web browser through the
router from the same Win95 client that fails with Eudora? If not, you have
bigger problems than I will consider here.
Next question: can you *send* mail through the router using Eudora? Sending
mail from Eudora uses the SMTP port (25), while receiving it uses POP3 (153,
I think) or IMAP (don't recall its port number) ... so the two can be quite
different.
Next question: what kernel version are you using, and what do your ipfwadm
(2.0.x) or ipchains (2.2.x) rules look like? Are you inadvertantly blocking
the POP3 port? This is my guess, but without checking your rules (and
knowing if you use POP3 or IMAP), I can't do more than guess.
Just to encourage you ... I'm running here from pretty much what you want to
set up. I use Eudora 2.2 on Win95 for my mail, and the workstation is on a
private LAN (192.168.1.0 network) that accesses the Internet through a
Debian-based router that IP Masq's. I also have a modem on the machine, and
I can, with NO reconfiguration whatsoever (except what the Win95 ppp package
does automatically), access my ISP either way -- through the router or
directly from my built-in modem.
To do this, I have TCP/IP stacks bound to both the Dial-Up Adapter and the
Ethernet adapter ... the only nuisance is that ppp offers me dialing
opportunities when I start new apps, but all I have to do is cancel and the
apps then route through the LAN and router. So I kind of doubt that your
problem is on the Win95 end (but I admit to only minimal expertise with
Win95, even though I use it for some everyday humdrum tasks).
At 09:32 AM 11/25/99 +0700, Shaggy Im-erbtham wrote:
>I just got IP Masq working at a rudimentary level, viz. I can manually log
>into my ISP
>manually with minicom and launch the browser from my win95 clients. The
>arrangement
>is stable even with three win95 clients simulataneously browsing the net.
>The browsers
>are Netscape 4.04 and Opera 3.x. I will eventually automate the log-ins and
>log-outs
>with ppp-on, ppp-off scripts.
>
>However, my problem is that my win95 client can no longer check or send
>mail with
>Eudora Pro 4.0. Not while IP Masq'ed through the Linux router. And not even
>when I
>tried direct connection with the modem MOVED to the win95 machine.
>
>The error messages are as follows:
>> Contacting [my.isp.domain.name] (192.168.1.3) <--this is IP add of
>the win95 client
>>Could not connect [my.isp.domain.name]
>>Cause: Connection refused (10061)
>
>This occurs in both instances: while connected to IP Masq router (modem on
>Linux router)
>and when direct dial-up was attempted from win95 (modem on win95).
>
>I know this is not a windows list but if anybody knows how to fix the
>problem, I would
>really appreciate it. The reason I was able to send this email is I had to
>reconfigure
>win95 to disable DNS (same nameserver info as in /etc/resolv.conf) from the
>TCP/IP stack
>bound to the machine's network card. Now this win95 machine is excluded from
>IP Masq. and I donot want to keep moving my single modem back and forth
>between two machines.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
