Re: [tcpconnect] doing nothing

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 37936
interpreted = N
texte = The server has been rebooted - more than once - and I have tried using the IP number instead of the domain name for UPS, to no avail...The exact same code running on my MacOS X server works fine, while on my client's Windows server I get no response at all from the [tcpconnect] context.Is there some system service that [tcpconnect] uses on Windows that may not be running an may be causing this problem?BrianAt 6:23 AM +0000 8/8/2001, Peter Werno wrote: >Hello Brian, > >as it is a Windows-Box, rebooting may help :-) >Something else that came to my mind was DNS setup. Maybe the Server >doesn't get the DNS-information for UPS? Have you tried using the >IP-Address instead? > >Just a guess... > >Ciao, > >Peter > >On Tue, 7 Aug 2001 15:35:43 > Brian Fries wrote: >> I have a client running WC 4.0.2 rc1 on a Windows box (not sure what >> windows - I assume some NT variant). In his checkout pages, the code >> is doing a TCPCONNECT to UPS, but absolutely nothing is being >> returned. When I run the exact same TCPCONNECT call on my Mac OS X >> server (same WC rev), it works perfectly fine. The key line is: >> >> [text show=f]fullResponse=[tcpconnect >> host=www.ups.com&port=80][tcpsend][msgOut][/tcpsend][/tcpconnect][/text] >> >> >> [msgOut] is correctly set (verified identical to that sent from my >> server), but when this is hit on his server, [fullResponse] comes >> back empty, while on my server it returns a proper response value. >> >> It is as though [tcpconnect] is doing nothing at all. I didn't do the >> original development on this site, but was called in to clean up the >> messes left behind by the previous developer. During earlier test >> cycles, this [tcpconnect] problem did not show itself, so I assume it >> was working fine. The code hasn't changed since then. >> >> ... one other odditity I found: when I put a [version] tag on this >> page, I get the value 1.5 returned, while the [version] tag on the >> admin statistics page returns the correct 4.0.2 rc1 value. Anyone >> seen this behavior before? >> >> Any thoughts or suggestions on getting the [tcpconnect] working >> properly? Would rebooting the machine be likely to help? >> >> Thanks, >> Brian >> -- >> <= Brian C. Fries, BrainScan Software >> http://www.brainscansoftware.com => >> >> ------------------------------------------------------------- >> 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 >> >> Web Archive of this list is at: http://search.smithmicro.com/ > > >------------------------------------------------------------- >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 > >Web Archive of this list is at: http://search.smithmicro.com/ ------------------------------------------------------------- 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 Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: [tcpconnect] doing nothing- SM any help here??? (Brian Fries 2001)
  2. Re: [tcpconnect] doing nothing- SM any help here??? (Jay Van Vark 2001)
  3. Re: [tcpconnect] doing nothing- SM any help here??? (Brian Fries 2001)
  4. Re: [tcpconnect] doing nothing (Brian Fries 2001)
  5. Re: [tcpconnect] doing nothing (Peter Werno 2001)
  6. [tcpconnect] doing nothing (Brian Fries 2001)
The server has been rebooted - more than once - and I have tried using the IP number instead of the domain name for UPS, to no avail...The exact same code running on my MacOS X server works fine, while on my client's Windows server I get no response at all from the [tcpconnect] context.Is there some system service that [tcpconnect] uses on Windows that may not be running an may be causing this problem?BrianAt 6:23 AM +0000 8/8/2001, Peter Werno wrote: >Hello Brian, > >as it is a Windows-Box, rebooting may help :-) >Something else that came to my mind was DNS setup. Maybe the Server >doesn't get the DNS-information for UPS? Have you tried using the >IP-Address instead? > >Just a guess... > >Ciao, > >Peter > >On Tue, 7 Aug 2001 15:35:43 > Brian Fries wrote: >> I have a client running WC 4.0.2 rc1 on a Windows box (not sure what >> windows - I assume some NT variant). In his checkout pages, the code >> is doing a TCPCONNECT to UPS, but absolutely nothing is being >> returned. When I run the exact same TCPCONNECT call on my Mac OS X >> server (same WC rev), it works perfectly fine. The key line is: >> >> [text show=f]fullResponse=[tcpconnect >> host=www.ups.com&port=80][tcpsend][msgOut][/tcpsend][/tcpconnect][/text] >> >> >> [msgOut] is correctly set (verified identical to that sent from my >> server), but when this is hit on his server, [fullResponse] comes >> back empty, while on my server it returns a proper response value. >> >> It is as though [tcpconnect] is doing nothing at all. I didn't do the >> original development on this site, but was called in to clean up the >> messes left behind by the previous developer. During earlier test >> cycles, this [tcpconnect] problem did not show itself, so I assume it >> was working fine. The code hasn't changed since then. >> >> ... one other odditity I found: when I put a [version] tag on this >> page, I get the value 1.5 returned, while the [version] tag on the >> admin statistics page returns the correct 4.0.2 rc1 value. Anyone >> seen this behavior before? >> >> Any thoughts or suggestions on getting the [tcpconnect] working >> properly? Would rebooting the machine be likely to help? >> >> Thanks, >> Brian >> -- >> <= Brian C. Fries, BrainScan Software >> http://www.brainscansoftware.com => >> >> ------------------------------------------------------------- >> 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 >> >> Web Archive of this list is at: http://search.smithmicro.com/ > > >------------------------------------------------------------- >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 > >Web Archive of this list is at: http://search.smithmicro.com/ ------------------------------------------------------------- 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 Web Archive of this list is at: http://search.smithmicro.com/ Brian Fries

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:

os 8.5 (1999) Using WebCat for product info requests (1997) required fields (1998) Grouping search fields, etc. (1997) Nested tags count question (1997) OT: Research Friendly Data Interface (2002) Taxable Shipping (2003) [ShowIf] and empty fields (1997) Emailer Q (2002) Searching for Nothing (1998) [WebDNA] 30 Minute Cookies (2016) No Data Results (1997) Help formatting search results w/ table (1997) Re:Emailer and encryption (1997) WebCat2b12 - nesting [tags] (1997) Separate SSL Server (1997) Stopping bad HTML propagation ? (1997) Searching & Hyphens (2002) EmailProblem vs EmailComplete (2000) Banners (1997)