If you have checked JINETD and INETDSEC, then I would suggest....

(1) run SOCKINFO.NET, and enter a "C" to display call sockets.  You
should have (among other things listed):

GLOBAL CALL/DATAGRAM SOCKET DISPLAY                                 
11:04 am

Port Addr     Pin T Prot User                       Program
-------------------------------------------------------------------------------
23.telnet     144 c tcp  jinetd,manager.sys         inetd.net.sys

(2) check SERVICES.NET and insure you have the (non-commented) line:

telnet       23/tcp

(3) try TELNET.ARPA.SYS 192.168.0.199 (from the 3000, telnet to itself,
make sure the service works)

If these things work properly, then the 3000's service is configured,
listening, and operating properly.  The problem must be between the PC
and 3000, possibly a firewall?  You have "some" connectivity and the
gateways are operating correctly if ping works in both directions as you
have described.

You might try getting NMAP for windows (http://nmap.org/download.html)
and try something along the lines of "nmap -sT 192.168.0.199" to see if
the service port is open, closed, or blocked from your PC's perspective.

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *