I’ve installed the beta of tcp/ip v5. I’m using tcp/ip for communication
between qnx and windows. The problem I’m having is that after installing
the new version my windows sockets program cannot connect to my qnx sockets
program. I can ping the QNX machine from windows, and I can ftp to the QNX
machine from windows. The error I’m getting in my windows program is
WSAECONNREFUSED. I don’t get any errors from the QNX sockets program. This
sounds like the ports I’m trying to use ( various ports in the 37000 range)
are no longer being allowed. Is there a tcp/ip configuration file that has
been changed that is now only allowing external machines to connect to the
standard ports such as those used with ping and ftp? Any help would be much
appreciated.
Thanks,
Rich Wells
Insight Control Systems
The problem was another machine on the network having the same ip address.
My requests were going to that machine, and were being refused because there
were no applications on that machine listening on those ports.
Thanks,
Rich Wells
“Operating System Tech Support” <os@qnx.com> wrote in message
news:9uleam$m9t$1@nntp.qnx.com…
“Richard Wells” <> rbw317@yahoo.com> > wrote in message
news:9uit4i$578$> 1@inn.qnx.com> …
I’ve installed the beta of tcp/ip v5. I’m using tcp/ip for
communication
between qnx and windows. The problem I’m having is that after
installing
the new version my windows sockets program cannot connect to my qnx
sockets
program. I can ping the QNX machine from windows, and I can ftp to the
QNX
machine from windows. The error I’m getting in my windows program is
WSAECONNREFUSED. I don’t get any errors from the QNX sockets program.
This
sounds like the ports I’m trying to use ( various ports in the 37000
range)
are no longer being allowed. Is there a tcp/ip configuration file that
has
been changed that is now only allowing external machines to connect to
the
standard ports such as those used with ping and ftp? Any help would be
much
appreciated.
That seems strange, does the problem go away if you use different ports
(ie
54321+)? Can you verify that your program is indeed listening (ie server
on
the QNX side) on port 37000 - do a netstat -an to view the connection
status. What happens when you telnet to the port 37000, do you still get
the refusal?
-Adam
“Richard Wells” <rbw317@yahoo.com> wrote in message
news:9uit4i$578$1@inn.qnx.com…
I’ve installed the beta of tcp/ip v5. I’m using tcp/ip for communication
between qnx and windows. The problem I’m having is that after installing
the new version my windows sockets program cannot connect to my qnx
sockets
program. I can ping the QNX machine from windows, and I can ftp to the
QNX
machine from windows. The error I’m getting in my windows program is
WSAECONNREFUSED. I don’t get any errors from the QNX sockets program.
This
sounds like the ports I’m trying to use ( various ports in the 37000
range)
are no longer being allowed. Is there a tcp/ip configuration file that
has
been changed that is now only allowing external machines to connect to the
standard ports such as those used with ping and ftp? Any help would be
much
appreciated.
That seems strange, does the problem go away if you use different ports (ie
54321+)? Can you verify that your program is indeed listening (ie server on
the QNX side) on port 37000 - do a netstat -an to view the connection
status. What happens when you telnet to the port 37000, do you still get
the refusal?
-Adam
“Operating System Tech Support” <os@qnx.com> wrote in message
news:9uohiq$vs$1@nntp.qnx.com…
“Richard Wells” <> rbw317@yahoo.com> > wrote in message
news:9ulv9k$9f6$> 1@inn.qnx.com> …
The problem was another machine on the network having the same ip
address.
My requests were going to that machine, and were being refused because
there
were no applications on that machine listening on those ports.
For future reference you can use the arp utility to see the arp table that
the stack is using. This should help you diagnose those kinds of problems
quickly.
Also a packet sniffer is also an invaluable tool to see where your
traffic is going/coming from.
Like the QNX4 utility netsnif !?!
-Adam
“Richard Wells” <rbw317@yahoo.com> wrote in message
news:9ulv9k$9f6$1@inn.qnx.com…
The problem was another machine on the network having the same ip address.
My requests were going to that machine, and were being refused because
there
were no applications on that machine listening on those ports.
For future reference you can use the arp utility to see the arp table that
the stack is using. This should help you diagnose those kinds of problems
quickly. Also a packet sniffer is also an invaluable tool to see where your
traffic is going/coming from.
-Adam
Thanks for the info.
Rich Wells
On Fri, 7 Dec 2001 02:32:54 -0500, “Operating System Tech Support”
<os@qnx.com> wrote:
“Richard Wells” <> rbw317@yahoo.com> > wrote in message
news:9ulv9k$9f6$> 1@inn.qnx.com> …
The problem was another machine on the network having the same ip address.
My requests were going to that machine, and were being refused because
there
were no applications on that machine listening on those ports.
For future reference you can use the arp utility to see the arp table that
the stack is using. This should help you diagnose those kinds of problems
quickly. Also a packet sniffer is also an invaluable tool to see where your
traffic is going/coming from.
-Adam
“Mario Charest” <mcharest@clipzinformatic.com> wrote in message
news:9uokor$8po$1@inn.qnx.com…
Also a packet sniffer is also an invaluable tool to see where your
traffic is going/coming from.
Like the QNX4 utility netsnif !?!
That would be one yes. Why the “!?!” in your post?
-Adam