We are using QNX nfs to mount a remote drive on an NT 4 machine. The QNX
machine is running QNX4.24 and TCP/IP 4.24. The NT 4.0 machine is running a
package called DiskShare which contains NFS software. When
a lot of files are written to the remotely mounted drive quite frequently we
get the Socket utility hanging. When we do a ls to the remotely mounted
drive the ls command hangs. If Socket is slayed and resarted long with a
reinvoke of th mount_nfs command all is well again. Our customer requires a
solution to this problem. Does this ring any bells. Would it be orthwhile
trying QNX 4.25 Socket ??
“Kevin Warkentin” <kevin.p.warkentin@ca.abb.com> wrote in message
news:98kv03$7l5$1@inn.qnx.com…
We are using QNX nfs to mount a remote drive on an NT 4 machine. The QNX
machine is running QNX4.24 and TCP/IP 4.24. The NT 4.0 machine is running
a
package called DiskShare which contains NFS software. When
a lot of files are written to the remotely mounted drive quite frequently
we
get the Socket utility hanging. When we do a ls to the remotely mounted
drive the ls command hangs. If Socket is slayed and resarted long with a
reinvoke of th mount_nfs command all is well again. Our customer requires
a
solution to this problem. Does this ring any bells.
Would it be orthwhile trying QNX 4.25 Socket ??
Definitely, but still TCP/IP 4.25 nfs support isn’t rock solid.
5.0 beta is MUCH better but it’s been in beta for a very very
long time, and has been in “release any time soon” state
for a few months.
Thanks Mario>
What about using the QNX4.25 Socket with the QNX4.24 nfs or would it be
better to install a complete QNX4.25 TCP/IP.
Can QNX 4.24 run with TCP/IP 4.25 software okay or do you have to have
QNX 4.25 running alongside TCP/IP 4.25 ?
“Mario Charest” <mcharest@void_zinformatic.com> wrote in message
news:98lodg$c15$1@nntp.qnx.com…
“Kevin Warkentin” <> kevin.p.warkentin@ca.abb.com> > wrote in message
news:98kv03$7l5$> 1@inn.qnx.com> …
We are using QNX nfs to mount a remote drive on an NT 4 machine. The QNX
machine is running QNX4.24 and TCP/IP 4.24. The NT 4.0 machine is
running
a
package called DiskShare which contains NFS software. When
a lot of files are written to the remotely mounted drive quite
frequently
we
get the Socket utility hanging. When we do a ls to the remotely mounted
drive the ls command hangs. If Socket is slayed and resarted long with a
reinvoke of th mount_nfs command all is well again. Our customer
requires
a
solution to this problem. Does this ring any bells.
Would it be orthwhile trying QNX 4.25 Socket ??
Definitely, but still TCP/IP 4.25 nfs support isn’t rock solid.
5.0 beta is MUCH better but it’s been in beta for a very very
long time, and has been in “release any time soon” state
for a few months.
\
“Kevin Warkentin” <kevin.p.warkentin@ca.abb.com> wrote in message
news:98nlgf$svc$2@inn.qnx.com…
Thanks Mario
What about using the QNX4.25 Socket with the QNX4.24 nfs or would it be
better to install a complete QNX4.25 TCP/IP.
I wouldn’t try that myself 
Can QNX 4.24 run with TCP/IP 4.25 software okay
or do you have to have QNX 4.25 running alongside TCP/IP 4.25 ?
I’m not 100% but I think you can use TCP/IP 4.25 with QNX4.24
“Mario Charest” <mcharest@void_zinformatic.com> wrote in message
news:98lodg$c15$> 1@nntp.qnx.com> …
“Kevin Warkentin” <> kevin.p.warkentin@ca.abb.com> > wrote in message
news:98kv03$7l5$> 1@inn.qnx.com> …
We are using QNX nfs to mount a remote drive on an NT 4 machine. The
QNX
machine is running QNX4.24 and TCP/IP 4.24. The NT 4.0 machine is
running
a
package called DiskShare which contains NFS software. When
a lot of files are written to the remotely mounted drive quite
frequently
we
get the Socket utility hanging. When we do a ls to the remotely
mounted
drive the ls command hangs. If Socket is slayed and resarted long with
a
reinvoke of th mount_nfs command all is well again. Our customer
requires
a
solution to this problem. Does this ring any bells.
Would it be orthwhile trying QNX 4.25 Socket ??
Definitely, but still TCP/IP 4.25 nfs support isn’t rock solid.
5.0 beta is MUCH better but it’s been in beta for a very very
long time, and has been in “release any time soon” state
for a few months.
\
Can anyone from QNX verify what Mario is saying ?
Can TCP/IP 4.25 run on a QNX4.24 system ?
- Thanks,
Kevin
“Mario Charest” <mcharest@void_zinformatic.com> wrote in message
news:98p6tr$e4t$1@nntp.qnx.com…
“Kevin Warkentin” <> kevin.p.warkentin@ca.abb.com> > wrote in message
news:98nlgf$svc$> 2@inn.qnx.com> …
Thanks Mario
What about using the QNX4.25 Socket with the QNX4.24 nfs or would it
be
better to install a complete QNX4.25 TCP/IP.
I wouldn’t try that myself >
Can QNX 4.24 run with TCP/IP 4.25 software okay
or do you have to have QNX 4.25 running alongside TCP/IP 4.25 ?
I’m not 100% but I think you can use TCP/IP 4.25 with QNX4.24
\
“Mario Charest” <mcharest@void_zinformatic.com> wrote in message
news:98lodg$c15$> 1@nntp.qnx.com> …
“Kevin Warkentin” <> kevin.p.warkentin@ca.abb.com> > wrote in message
news:98kv03$7l5$> 1@inn.qnx.com> …
We are using QNX nfs to mount a remote drive on an NT 4 machine. The
QNX
machine is running QNX4.24 and TCP/IP 4.24. The NT 4.0 machine is
running
a
package called DiskShare which contains NFS software. When
a lot of files are written to the remotely mounted drive quite
frequently
we
get the Socket utility hanging. When we do a ls to the remotely
mounted
drive the ls command hangs. If Socket is slayed and resarted long
with
a
reinvoke of th mount_nfs command all is well again. Our customer
requires
a
solution to this problem. Does this ring any bells.
Would it be orthwhile trying QNX 4.25 Socket ??
Definitely, but still TCP/IP 4.25 nfs support isn’t rock solid.
5.0 beta is MUCH better but it’s been in beta for a very very
long time, and has been in “release any time soon” state
for a few months.
\