HP3000-L Archives

November 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Korb <[log in to unmask]>
Reply To:
John Korb <[log in to unmask]>
Date:
Fri, 5 Nov 1999 14:09:10 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (57 lines)
Here is a brief overview of dozens of responses, but first, thanks to all
who responded!  I've really received quite a volume of email, with only a
small fraction of it echoed to the list!

I was able to get telnet to work when I changed the port number to 41 in
SERVICES.NET.SYS.  QCTerm connected and operated great.  Reflection
connected and operated great.  As long as I changed the SERVICES.NET.SYS
file on another HP 3000, I could have the two HP 3000's telnet to each
other without problems.  So, telnet is not a problem.

The Navy systems are on 5.5, so since ftp isn't running under inetd, it was
doubtful that changing SERVICES.NET.SYS would affect the client or server.
That assumption proved correct.  Changing the SERVICES file had no effect
on either the ftp client or server running on the HP 3000.  One fellow who
is on 6.0 wrote that he will try changing SERVICES on his system on the
weekend to see if ftp pays attention to SERVICES on 6.0.  I'll be
interested in his results.

As for ping, Jeff Kell and others pointed out that ping doesn't use a port
per se, so changing SERVICES shouldn't affect ping.  It didn't.  I tried it
and changing SERVICES had no effect.

Since I first wrote, a number of additional firewall changes have taken
place.  Now remote spooled printing is down.  It appears that SNMP is now
being blocked and so the HP 3000's can't check the status of their remote
spooled printers.

As a frustrated user complained this morning, "what good is all this
wonderful security if we can't get the job done?".

Oh well...

Thanks again to all for their help, their experiments, their suggestions,
and their time!

John


At 11/4/99 04:51 PM , John Korb wrote:
>Does anyone have experience configuring and using a port other than 23 for
>telnet?  What about ftp?  What about ping?  For telnet and ftp it looks
>like it might be possible to change the port numbers in services.net.sys.
>Before I try it, any comments?
>
>Any why would anyone want to do such a thing?  The Navy has decided to
>block ports 7, 21, and 23, incoming and outgoing.  No exceptions.  Guess
>where that leaves us?
>
>Thanks!

--------------------------------------------------------------
John Korb                            email: [log in to unmask]
Innovative Software Solutions, Inc.

The thoughts, comments, and opinions expressed herein are mine
and do not reflect those of my employer(s), or anyone else.

ATOM RSS1 RSS2