But with the aid of the test results, the solution may take a few minutes, instead of hours or days. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. Is there something that I can do to change the behavior of the Mac telnet client? I'm wondering what other people have done to workaround this annoyance? Using the Windows telnet client, it would never report that it was connected if the TCP three-way handshake did not complete.ฤก. I also confirmed this by installing SecureCRT on the Mac - when I try to telnet to the same host on the same port, it never connects. If I type anything into the prompt when it's "connected", I don't see any of those packets actually being sent from my Mac to the remote host. and yet the telnet client is saying that it's "connected". I ran a WireShark trace and only saw the SYN packet, but no SYN-ACK packet from the remote host. I'm trying to establish a TCP connection to another host on my network that isn't listening on the port I'm trying to connect to, but Mac still reports that it's "connected". I discovered that the telnet client on my Mac reports that it's "connected" when it actually isn't. I'm a network engineer, and I'm starting to think that switching from a PC to a Mac just wasn't a good choice.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |