lafleur@sicsun.epfl.ch (Bill La Fleur) (05/30/91)
Okay folks, I got a weird one for ya: There's a guy here working on a MacIICI trying to FTP to acouple of sites outside the EPFL. He can telnet to these sites no problem, but when he FTP's there he gets a msg saying "Gateway not responding" or something to that effect. Now, like I said, we can telnet to these sites no problem, so they're up. And I, on my machine, can ftp to them just fine. And from his machine we can FTP to any site we like ==> here at EPFL <===. I replaced the MacTCP drivers, though they were the correct version and looked fine to me - this did nothing. I replaced his copy of TCP/Connect II (v. 1.0.7), though it seemed to be working fine too - this did nothing. We then tried VersaTerm, going through the CTB with a tool they have written (I'm foggy on this one, its the first time I'd seen the stuff.), and that didn't work either, for the same reason: "Gateway not responding" type msg. Using a terminal sitting right next to the Mac, connected via a CS200 to Ethernet, we could telnet anywhere and ftp anywhere, so it isn't like there's a problem with the Ethernet itself. And like I said, sitting at my Mac, using ftp, or Xferit, or telnetting to a Unix machine and then ftp'ing, all work. So what's his problem? Must be at the MacTCP level if two Apps have the same problem right? Well before I put a Sniffer on there and spend hours hacking away at this stuff, does anybody have any ideas? Oops, forgot: I also did all this with all INITs canceled except for the essentials, including MacTCP, so it doesn't seem to be a conflict of an INIT or whatever with MacTCP... Oops, one more detail: he's hooked up directly to Ethernet via a card from Apple, we run EtherTalk Phase II here, and he's got all the necessary drivers working fine... Thanks for any help, I'll re-post once I've got a definitive solution to the problem. Suggestions like an exorcism or telling the user that its his fault have already been considered... :-) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +Send all replies, advice, love letters to lafleur@sicun.epfl.ch. + +*** Look Mom! My first disclaimer!!! *** + Disclaimer: Nothing I+ ++++++++++++++++++++++++++++++++++++++++++++++ say would ever be + + No, we're never gonna survive, + claimed by EPFL - + + Unless we get alittle bit + they haven't got the + + - Seal + guts... + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Metamorphosis (06/01/91)
In article <1539@sicsun.epfl.ch> lafleur@sicsun.epfl.ch (Bill La Fleur) writes: > Using a terminal sitting right next to the Mac, connected via a CS200 to >Ethernet, we could telnet anywhere and ftp anywhere, so it isn't like there's a >problem with the Ethernet itself. And like I said, sitting at my Mac, using >ftp, or Xferit, or telnetting to a Unix machine and then ftp'ing, all work. So >what's his problem? Must be at the MacTCP level if two Apps have the same >problem right? Well before I put a Sniffer on there and spend hours hacking >away at this stuff, does anybody have any ideas? > > Oops, forgot: I also did all this with all INITs canceled except for the >essentials, including MacTCP, so it doesn't seem to be a conflict of an INIT or >whatever with MacTCP... One suggestion from an empirical problem-solver: try it from your Mac after starting up from an appropriately configured System Folder on a floppy. If it works, take the floppy to his Mac, start up from it, and try to do exactly the same thing. If that fails, your problem's gotta be hardware, either the Mac itself (are you using a IIci? could it be a problem with the IIci as a class?), or the ethertalk connection. God or an army of gurus help you if that's the case... Fortune! |--------------------------------------| | No, I don't have a sig. Actually, I | | don't even have an e-mail account at | | the moment... | |--------------------------------------|