I have a new HP 3000 A-500 installation that I can't Telnet to. Ping works both ways, but I get nothing with Reflection's Telnet. What do I need to check on the 3000 to get Telnet running?
Robert Schlosser says:
Donna Hofmeister adds:
There's a collection of 'samp' files in .NET that in most cases need to be copied to their 'real' file name in order to make TCP/INETD networking work.
Hofmeister, one of the community's more experienced hands with the standard Unix and Posix utilities built into MPE/iX and the HP 3000, explains.
The samp files are
BPTABSMP -- bootptab (most people don’t use)
HOSTSAMP -- hosts
INCNFSMP -- inetd configuration
INSECSMP -- inetd security
NETSAMP -- reachable networks
NSSWSAMP -- nsswitch
PROTSAMP -- protocol
RSLVSAMP -- DNS resolving
SERVSAMP -- services
I believe each of the files also has a counterpart in /etc which is a link to the real file in .NET.SYS. If the real files are missing from .NET.SYS then many things (including Telnet and FTP) won’t work.
Craig Lalley wonders:
How are your gateways defined? If you change the gateway
then you could try deleting the wrong gateway and see if it helps. You may have a router broadcasting a wrong gateway.
Hofmeister says the problems might be in the physical layer:
Did you change NMMGR before or after the reboot? If after, you're going to want to reboot again. Your packet loss is disturbing. I'd be suspicious of a physical layer problem.
Problems in the physical layer can be addressed by replacing parts, Mark Landin advises.
- Could be a bad network cable or connector. Replace them.
Could be a bad network switch port. Connect the system to another port (properly configured, of course).
- Could be a bad NIC. Swap them in the 3000 and see if the problem moves with the card.
Hofmeister points back to TCP timer issues"
On PCI (A- and N-Class) systems with 100bt cards, you're more likely to see 'recv dropped: addr' counts due to the way the card handles (or not, actually) traffic routed for a different destination.
Typically these counts are nothing to be concerned about. What is concerning are the TCP statistics. Retransmits are almost always a function of using the default (or otherwise messed up) TCP timers.