Re: TCPConnect misbehavin' for me.

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 27646
interpreted = N
texte = > >Which means the request never gets there. This could mean a webcat bug ... > >Or if the remote server does not log requests it's too busy to >handle, the request is actually coming in but it's just not being >logged, which means it's a 'busy server' problem ...It's Communigate Pro on Linux and it is only handling this job so it's mostly idle at this point.>Or there's a network problem that's preventing the requests from >getting to the remote server even though they are being sent via >webcatalog ...Same hub IP...190 & ...191. Nothing else on that network has any problems.>To see if webcatalog is actually sending the request, run >OTSessionWatcher on the server, and see if it logs the tcpconnect ...Can't run OTSessionWatcher, Server A is OSXS.Thanks Ken, do you have any other suggestions. It just screwed up again.Charlie ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Associated Messages, from the most recent to the oldest:

    
  1. Re: TCPConnect misbehavin' for me. (Kenneth Grome 2000)
  2. Re: TCPConnect misbehavin' for me. (Charlie Romero 2000)
  3. Re: TCPConnect misbehavin' for me. (Kenneth Grome 2000)
  4. Re: TCPConnect misbehavin' for me. (Charlie Romero 2000)
  5. Re: TCPConnect misbehavin' for me. (Kenneth Grome 2000)
  6. Re: TCPConnect misbehavin' for me. (Charlie Romero 2000)
  7. Re: TCPConnect misbehavin' for me. (Kenneth Grome 2000)
  8. Re: TCPConnect misbehavin' for me. (Rob Marquardt 2000)
  9. TCPConnect misbehavin' for me. (Charlie Romero 2000)
> >Which means the request never gets there. This could mean a webcat bug ... > >Or if the remote server does not log requests it's too busy to >handle, the request is actually coming in but it's just not being >logged, which means it's a 'busy server' problem ...It's Communigate Pro on Linux and it is only handling this job so it's mostly idle at this point.>Or there's a network problem that's preventing the requests from >getting to the remote server even though they are being sent via >webcatalog ...Same hub IP...190 & ...191. Nothing else on that network has any problems.>To see if webcatalog is actually sending the request, run >OTSessionWatcher on the server, and see if it logs the tcpconnect ...Can't run OTSessionWatcher, Server A is OSXS.Thanks Ken, do you have any other suggestions. It just screwed up again.Charlie ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Charlie Romero

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

searchable list archive (1997) Using [sendmail] for mass mailings (2001) MacWEEK article help needed (1996) [WebDNA] Premature end of script headers: (2013) Reference data: ip-to-country (2004) Running _every_ page through WebCat ? (1997) Strange database format import (2000) Less than or equal to........ (1997) Checkboxes (1998) [include ...] behavior (1997) Frames (1997) About the E-mailer (2002) webDNA language. (2004) Major Security Hole (1998) SETCOOKIE Tricks (2003) E-Mail Preferences in Admin Folder (1997) Getting Total Quantity (1997) [WebDNA] path traversal (2020) Re:E-mailer application times out (1998) OT: Alias/Shortcut on Windows server (2003)