• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
TCP Connect Failures
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

TCP Connect Failures


  • Subject: TCP Connect Failures
  • From: Steven Fisher <email@hidden>
  • Date: Fri, 01 Mar 2002 17:22:41 -0800

I need a way to detect either if TCP is turned off, or if dial out fails. Is
there any easy way to do this?

At first, I tried to use NetworkSetup. However, it just won't work in my
project. I'm not really sure why, but if there's a simpler way I'd rather
take it.

Next, I tried checking to see if the TCP stack was loaded after calling
OTConnect. This always seems to be the case, even if I have no active
network ports. (This is still a classic app, but it's being developed under
Mac OS X.)

Basically, I want to report to the user either that a TCP connection isn't
going to work in advance or (if that's unachievable) has failed due to
configuration problems. Reporting the same error message for connectivity
down vs. unable to connect to my host has been deemed unacceptable. :(

I have been searching for answers relating to this for a while, and I'm a
week past deadline. Any ideas? Please help if you can! :)
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: help: Can not find the appletalk printer in carbon shared library
  • Next by Date: Re: "TCP/IP Preferences" files fill my FCB pool
  • Previous by thread: help: Can not find the appletalk printer in carbon shared library
  • Next by thread: MoreSCF Published
  • Index(es):
    • Date
    • Thread