Subject: Re: ddp/tcp connections (pre-39): For Me, Sorta Solved...
From: Reed Loefgren (reedloefgren@interfold.com)
Date: Mon Aug 14 2000 - 22:52:43 EDT
Harry,
I've sorta solved my problem. Here's a rather lengthy synopsis of what
works for me (but it isn't a perfect world, and I use MacOS/bootX. Don't
know what the deal would be with OF booting):
Appletalk control panel set to: Connect via Ethernet.
TCP-IP control panel set to: Connect via Ethernet.
Configure: set to Manually.
Use 802.3 was checked because I could, not because I know what it does.
(I have since unchecked this.)
IP address set to 192.168.1.2 (the same address I use when my box is
booted into Linux.)
Subnet mask left blank to force it to the default for the IP address (it
would be 255.255.255.0, I think.)
For Name server addr. I just put the IP address of my server (a stab,
that.)
Close the window to save the settings and bring up the chooser. If I
click on the Appletalk icon I get the server's name, just the name and
not the fqdn. If I click on the Server IP Address button and key in the
server's IP address the barber pole runs forever. I then cancel and
select the server's name from the box, click on the OK button and after
a short wait the connect box comes up.
I accept the username and password remaining from the last connection,
hit the Connect button, then the OK button and I have...an Appletalk
connection. So it does fall back to Appletalk when using the chooser to
connect.
A re-boot brings it up as a TCP-IP connection (nice!) only if, in the
TCP/IP control panel, the TCP connection sub-window is "Active" and the
"load when needed" option is UNCHECKED. But then I can't dial out to my
ISP via modem. I have to go back into the TCP control panel and change
Connect via: to PPP. This stinks. You'd think MacOS could keep track of
two different protocols on two entirely different physical connections
(ethernet port for the network connection, and the modem port for, well,
the modem. (Linux 1, MacOS 0.))
So that was the logjam in my case: because the Ethernet data was
entered I was thinking that MacOS could/would use them, so I went and
set "Connect via:" to ppp because that is what my modem needed to work.
This actually killed the TCP connection to the server and it
consistantly, quietly fell back to appletalk. That stinks too.
I would imagine I can get my ISP's data entered in somewhere so that I
might keep the Ethernet connection and not blow out my PPP connection,
but I'm taking a rest from this one.
Thanks to everyone who keeps posting their on-going problems with
this; it helped me get off my duff and keep playing with things. And I
hope this information helps someone with their headache. I'm open to
further questions to clarify the above.
Reed
Harry Zink/Netatalk List wrote:
>
> on 8/14/00 11:02 AM, Reed Loefgren at reedloefgren@interfold.com wrote:
>
> > This is EXACTLY what I'm seeing; Command-I says connected via Appletalk,
> > and believe me, the speeds I'm getting seem to bear this out. TCP-IP is
>
> SO, at the very least there is an issue with assigning the proper icon in
> pre-39 (at least), as well as whatever Reed is using.
>
> I'll check the DNS issue (I know I'm not running a DNS'd box in my
> mini-network where this is being tested), so I'll see if the errors go away
> once I make this box resolve itself properly.
> Harry
> --
> CAN'T SEE MAC IN CHOOSER UNDER RedHat 6.2: If you get errors starting
> AppleTalk under RedHat 6.2 and Mandrake 7.1, you need to manually add "alias
> net-pf-5 appletalk" to your /etc/conf.modules file.
--The promise of the Machine Age was to increase Leisure, not Productivity.
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:31:59 EST