CompuServe Thread

#TCP/IP doesn't to OS/2

10 messages in this thread
#67638From: Robert SandersAug 28, 1992 9:15 PM
I have TCP/IP 1.2.1 up and running on my OS/2 PC and the Amiga TCP/IP running on my Amiga. The PC will connect to the Amiga via FTP, but I can't do anything once I've connected. Any command I try times out. The Amiga won't connect to the PC at all. It times out attempting to FTP [hostname] I can ping the PC from the Amiga and ping the Amiga from the PC. I can also ping the Amiga from the Amiga, but the PC won't ping itself. I checked the net addresses, and everything looks OK there. Two hosts, and the net numbers agree on both machines. ICAT on the PC shows the same number as that for the PC. What sort of mistake have I made? BobS "Think of it as evolution in action"
#67669From: Don Curtis/SYSOPAug 29, 1992 12:44 AM
Bob, When we had similar problems on some of our UNIX boxes at work, we found the broadcast addresses had to be set at either all 1's or all 0's (I forget now which was required…I believe it had to be all 1's). Don
#67718From: Robert SandersAug 29, 1992 2:05 PM
Don– Thanks. I'll try that and get back to you. Bob
#67756From: Robert SandersAug 29, 1992 9:27 PM
Don, >>When we had similar problems on some of our UNIX boxes at work, we found the broadcast addresses had to be set at either all 1's or all 0's (I forget now which was required…I believe it had to be all 1's). It turned out to be the usermask value rather than the broadcast address. If I set the usermask to 255.0.0.0, everything worked fine. I have no idea why, except that the loopback addresses may have conflicted with the network addresses. BobS "Think of it as evolution in action"
#67793From: Don Curtis/SYSOPAug 30, 1992 2:27 AM
Bob, Ok…that would have been my next suggestion…what's called 'netmask' on our UNIX boxes apparently is called 'usermask' on yours. Don
#67901From: Robert SandersAug 30, 1992 7:48 PM
Don, Thanks for all your help. Everything is working well now. I can ftp both ways, the NFS server on the PC loads fine and exports all its partitions for the Amiga to mount them. A few little problems: (1) the PC doesn't support RCP. (2) the Ami doesn't support LPR. With NFS, I don't need RCP, and I think that I can work around the LPR problem by using CMD, PrintFiles, and ftp in a script under ADOS or AREXX. All in all, everything works very well and it is a good solution for anyone that has to connect an Amiga to a PC that is running OS/2. I know that there are TCP/IP offerings for both Windows and DOS, but I have never used them, so I can't recommend them as a solution. The PC software and hardware was cheaper than the Amiga software/hardware ($100 for the ethernet board, $170 for TCP/IP, and $100 for NFS server on the PC vs $300 for the ethernet board and $200 for TCP/IP on the Ami), and the documentation is considerably more complete for TCP/IP for OS/2. BobS "Think of it as evolution in action"
#67951From: Don Curtis/SYSOPAug 30, 1992 11:31 PM
Bob, Hummm…who's implementation of TCP/IP are you using on the OS/2 machine? We use PC/TCP from FTP software on our DOS boxes…but it's about $500 a crack. Don
#68090From: Robert SandersAug 31, 1992 10:04 PM
Don, I'm using IBM's implementation on a clone. And I misremembered (overstated) the price! TCP/IP for OS/2 part # 02G6968 list $200 retail $132 NFS for OS/2 part # 02G6970 list $150 retail $100 The NFS program provides NFS client _and_ server support. IBM also offers X-Windows support part # 02G6980 for an additional $150 ($100 retail). I also called a company for a Windows version of TCP/IP (they have an ad in InfoWeek). I think that the product was called Chameleon (I dont remember the company) and went for appx $300. It installs as a Windows DLL and needs only 6KB of real memory. The ad said that it supports NFS, but I don't know if that is server, client, or both. If you would like, I can post the phone# for you. BobS "Think of it as evolution in action"
#67960From: KEITH YOUNGAug 31, 1992 12:56 AM
Quick question… why would you need/use ftp ? Once you have the PC volumns mounted on your Amiga, you can just access them like your Amiga drive(s). – Keith
#68091From: Robert SandersAug 31, 1992 10:04 PM
Part of the problem was that the NFS server didn't come up (perhaps IBM's implementation won't come up if there are comm problems). I was using ftp to test the communications link. FTP is also one of the approaches that I can use to print on the PC. I got the problems straightened out though. It seems as though the subnet (user) mask was incorrect (too restrictive). Don provided a an answer to my question that pointed me in the right direction. Once I fixed that problem, everything worked fine except reads from the NFS volumes, until I changed the NFSMGR MOUNT commands to include maxread=4096. Now that everything works (and I wish that Amiga TCP/IP supported LPR), all that I have to do is decide _how_ I am going to print to the PC from the Amiga (ftp or rsh). BobS "Think of it as evolution in action"