Forums

You may post here on any subjects related to this site or the software therein. (Most everything on this site is tied into the forums so that you may leave or post comments about it.)

   

TCP Client problem with NT 4.0?

   From: Urs
   Date: January 04 2002 12:50 AM
I built an application using the tcp client with CF. It is working great - on my machine using W2K. When I put it onto an NT 4 server (within the same network), I cannot create connection to the dll, the object is not created, I receive a "0".
The dll has been successfully registered. What else could be the matter?

Any idea?

Urs

RE:TCP Client problem with NT 4.0?

   From: Urs
   Date: January 04 2002 3:23 AM
I found and tried CFX_TCPCLIENT: again, it is working great on my machine, but fails on the NT4 Server. The error message received is:

SOCKET is invalid. [Line 684, v1.1]. SELECT(write) Socket Error (10038) (null) [Line 219, v1.1]. SEND Socket Error (10038) (null) [Line 231, v1.1].

10038 tells me that there is no open socket when expected. (http://www.sockets.com/winsock.htm is a good source, but my understanding is too limited)

my code reads:


<CFX_TCPClient
SESSION="OPEN"
HOST="212.215.24.38"
PORT="2711"
SOCKETNAME="telnetsocket"
>

<!--- Send out the message --->
<CFX_TCPClient SENDRN=#variables.sendPage# SOCKET="#telnetsocket#">

<!--- get returned messages --->

<CFX_TCPClient WAITFORRECVDATA="3" RECV="telnet" SOCKET="#telnetsocket#">


<!--- set returned messages for further processing --->
<CFIF len(TCPClientError) gt 0>
<cfset response=#TCPClientError#>
<cfelse>
<cfset response=#variables.telnet#>
</CFIF>

<cfoutput>
<cfset CALLER.response=#variables.response#>
</cfoutput>

But when I do the connection manually in a command window, it works fine.
winsock.dll is the same version on both systems, 'Everyone' can read, write, execute, modify.
On that server I have CF5, but I develop on CF 4.5.1 SP2.

Please HELP someone!?!

Urs

RE:TCP Client problem with NT 4.0?

   From: Urs
   Date: January 04 2002 3:25 AM
And finally my third and last message for today - containing the code promised above:

<CFX_TCPClient
SESSION="OPEN"
HOST="212.215.24.38"
PORT="2711"
SOCKETNAME="telnetsocket"
>

<!--- Send out the message --->
<CFX_TCPClient SENDRN=#variables.sendPage# SOCKET="#telnetsocket#">

<CFIF len(TCPClientError) gt 0>
<cfset CALLER.response="#TCPClientError# on sending message">
<CFEXIT METHOD="EXITTAG">
</CFIF>

<!--- get returned messages --->

<CFX_TCPClient WAITFORRECVDATA="3" RECV="telnet" SOCKET="#telnetsocket#">


<!--- set returned messages for further processing --->
<CFIF len(TCPClientError) gt 0>
<cfset response="#TCPClientError# on receiving message">
<cfelse>
<cfset response=#variables.telnet#>
</CFIF>

<cfoutput>
<cfset CALLER.response=#variables.response#>
</cfoutput>

Urs

RE:TCP Client problem with NT 4.0?

   From: Urs
   Date: January 04 2002 3:28 AM
O.k., I lied. And already made a fool of myself. But I do keep promises:



<CFX_TCPClient
SESSION="OPEN"
HOST="212.215.24.38"
PORT="2711"
SOCKETNAME="telnetsocket"
>

<!--- Send out the message --->
<CFX_TCPClient SENDRN=#variables.sendPage# SOCKET="#telnetsocket#">

<CFIF len(TCPClientError) gt 0>
<cfset CALLER.response="#TCPClientError# on sending message">
<CFEXIT METHOD="EXITTAG">
</CFIF>

<!--- get returned messages --->

<CFX_TCPClient WAITFORRECVDATA="3" RECV="telnet" SOCKET="#telnetsocket#">


<!--- set returned messages for further processing --->
<CFIF len(TCPClientError) gt 0>
<cfset response="#TCPClientError# on receiving message">
<cfelse>
<cfset response=#variables.telnet#>
</CFIF>

<cfoutput>
<cfset CALLER.response=#variables.response#>
</cfoutput>


Urs ;-o

RE:TCP Client problem with NT 4.0?

   From: Lewis A. Sellers
   Date: January 04 2002 12:26 PM
Well, the short answer is that I haven't touched a copy of NT4 in probably a little over a year. As I recall CFX_TCPClient 1.x (not the current 2.x COM version) was developed under NT 4 SP5 or SP6.

While CFX_TCPClient is known to have ran under NT4 it was also buggy as hell. So I really wouldn't trust it for production code.

Some answers are: Does the NT4 server have the last service packs? And most importantly, is there a firewall issue for the NT4 server? ie Can you PING or TRACERT from the NT4 to the target ip?

It would help if you post the COM's full error string, if any, after returning 0.
(Currently tcpclient 3.x is laying in a several unfinished pieces so if there is a slight problem it may be a while before I can post an update.)

--min


RE:TCP Client problem with NT 4.0?

   From: Urs
   Date: January 05 2002 2:50 AM
Thanks so far - and for the quick reply! I'll continue working with COM and CFOBJECT, where I am encountering the same problem.

I'll try to get more error information. I do not expect it to be a firewall problem because I can send a string to that address via telnet console of NT4. Perhaps there are some default parameters set in "NT4 telnet" that make it work with the NT4 console but not when accessing winsock directly...?

I am using Service Pack 6a, so that is hardly the problem.

All the best,

Urs

RE:TCP Client problem with NT 4.0?

   From: Urs
   Date: January 09 2002 3:48 AM
I made some further tests
The error message I get is:

'[tcp.cpp Line 198] No such host? (212.215.24.38)'

When I activate PGPnet on my local Machine (to simulate a firewall that forbids connection), I get

'tcp.cpp Line 251] Connect error: socket=764 host=212.215.24.38 port=2711 (10060)'

So I do not think it is a firewall issue. Could it be that the NT telnet console uses some default parameters which I do not know of?

Do you have another idea?

Thanks in advance,

Urs

RE:TCP Client problem with NT 4.0?

   From: Urs
   Date: January 25 2002 9:47 AM
Dear Lewis,

I know you do not have to give me support on this one. but since I am unable to read and UNDERSTAND the source code, especially what the cause of the message 'No such host?' could be, I am asking you to let me know if you have any idea what the reason for the message could be. Any hint would be helpful.

If you think it would take more time to investigate, we certainly could talk about money we'd pay you for your efforts. What's your price?

Thanks a lot in advance,

yours, Urs
Copyright © 1997-2006 by Lewis A. Sellers.        Login