The setup consists of one RTP “server”, some RTP workstations and QNX4
workstations. They are all on the same segment 192.168.2.X.
The RTP server happily serves ftp, telnet, phindows, nfs, but no one
can ping to it? At first I though this was because of something the
network guys did with their fancy switches, but they swear
they have nothing to do with this. All the other machines can
ping themselves without problem.
I’m baffled, what could cause this?
can it ping it self on all interfaces?
Mario Charest wrote:
The setup consists of one RTP “server”, some RTP workstations and QNX4
workstations. They are all on the same segment 192.168.2.X.The RTP server happily serves ftp, telnet, phindows, nfs, but no one
can ping to it? At first I though this was because of something the
network guys did with their fancy switches, but they swear
they have nothing to do with this. All the other machines can
ping themselves without problem.I’m baffled, what could cause this?
- Mario
Yes.
“Rick Lake” <rwlake@SPAM.REDIRECTED.TO.DEV.NULL> wrote in message
news:3ACDC8B4.31DBD5C6@SPAM.REDIRECTED.TO.DEV.NULL…
can it ping it self on all interfaces?
Mario Charest wrote:
The setup consists of one RTP “server”, some RTP workstations and QNX4
workstations. They are all on the same segment 192.168.2.X.The RTP server happily serves ftp, telnet, phindows, nfs, but no one
can ping to it? At first I though this was because of something the
network guys did with their fancy switches, but they swear
they have nothing to do with this. All the other machines can
ping themselves without problem.I’m baffled, what could cause this?
- Mario
I could suggest some test like placing the suspicious machine in a
simple network setup with another machine (with a simple hub or a
cross-cable) and see if it works, but from your previous posts I
consider you to be knowledgeable enough to think of this yourself 
Even though your network guys believe they didn’t do anything, they
could’ve done something unknowingly… I find it strange that services
like telnet and ftp would work, but not ping. This would suggest some
sort of firewalling (ACLs) in there somewhere.
Mario Charest wrote:
Yes.
“Rick Lake” <> rwlake@SPAM.REDIRECTED.TO.DEV.NULL> > wrote in message
news:> 3ACDC8B4.31DBD5C6@SPAM.REDIRECTED.TO.DEV.NULL> …
can it ping it self on all interfaces?Mario Charest wrote:
The setup consists of one RTP “server”, some RTP workstations and QNX4
workstations. They are all on the same segment 192.168.2.X.The RTP server happily serves ftp, telnet, phindows, nfs, but no one
can ping to it? At first I though this was because of something the
network guys did with their fancy switches, but they swear
they have nothing to do with this. All the other machines can
ping themselves without problem.I’m baffled, what could cause this?
- Mario