last night, i tried to connect my 7500/100 running mac os 8.1 to my macintosh IIsi running a/ux 3.0.1, appletalk worked, and i could successfully (after switching to ethernet) connect them via appletalk and mount a server volume, but when i got to trying out telnet, it didn't work, i used NCSA telnet and BetterTelnet 2, nwither worked, i typed in the ip address of the a/ux box (i have set up tcp/ip on the a/ux box in the commandshell) and it said connection lost or somthing like that i am suspecting the a/ux box having problems, not being set up properly, but i don't know, please help!
Bridged chat on:
Please support the defense of Ukraine.
Direct or via Unclutter App
Active forum topics
No Social Media.
All Content Locally Hosted.
Two Terabytes and Growing.
Built on Free Software.
We have complied with zero government requests for information.
i assume you are on a router. restart the router.
nope, not a router, an ethernet crossover cable
Did you set up TCP/IP on both machines? Did you put them on the same subnet (i.e. - A/UX machine is set to 192.168.0.2 and the MacOS machine is set to 192.168.0.3 or similar) with the correct subnet mask (255.255.255.0)?
yes, A/UX is configured as 192.168.1.5 and the powermac is 192.168.1.8, the powermac is on 255.255.255.0 subnet, but the A/UX box is on the default subnet (whatever it is for the thing, somthing like fx000000f or somthing (that;s not it but it's that format, or similar anyway) ) whats strange is that i can telnet from the a/ux box to the powermac when the powermac is running a program called chat2.1pre11 or somthing similar(it is a talnet based chat program), and it works fine, even appletalk pro works, it just dosn't make sense!
Telnet is by it's nature insecure. Perhaps they close the port to it or firewall it or use a nonstandard port or something. I don't know A/UX well enough to troubleshoot that, though. I've never even seen A/UX running.
I'm assuming the telnet server (telnetd) is running on the A/UX box, right? (ps -aux | grep telnet if you're not sure).
it runs inetd until it sees network access, then it starts the required deamons