02-22-2002
yeah i have a server running at home port 119 cos its always open from work,,,
my question is about a remote server on port 22. i can ssh out of the network, but port 22 is blocked incomming,,, it seems to mess up login via the keys..
the remote machine is actualy an NT machine running some sort of linux shell,,,, i dont how,,
but a uname -a says MS NT 5 i686
my client is solaris running openssh
dont know if that makes a difference
8 More Discussions You Might Find Interesting
1. Cybersecurity
Just out of curiosity, I see a lot of people here use Linux IPTables as their firewall.
Anyone here use something else like OpenBSD PF or *BSD IPF, IPFW?
I'm quite fond of OpenBSD and their Packet Filters. I find their syntax much easier to manage and from my personal experience, I find them... (5 Replies)
Discussion started by: tarballed
5 Replies
2. Cybersecurity
Would it be possible to restrict access to internet pages in the following way?
A machine:
IP = 128.1.17.123
Only pages from domains of the type "go.jp" and "ne.jp" are viewable. All others are not viewable or only partly viewable.
B machine:
IP = 128.1.17.146
Regardless of the domain... (4 Replies)
Discussion started by: mntamago
4 Replies
3. Solaris
Hi,
So that potential responders will have an idea of what they're dealing with let me say that while I am a UNIX newbie I have been in IT for over 10 years.
We have several SUN boxes running ver 5 of the OS that have been sitting dormant for some time as they were part of a now defunct... (3 Replies)
Discussion started by: pjewett
3 Replies
4. Cybersecurity
hi everyone
I am a newbee to firewall scripting. cannot understand how to write rules per host. in ip6tables.
anyone plz:( (2 Replies)
Discussion started by: xecutioner
2 Replies
5. Solaris
I am a complete UNIX neophyte with the unenviable task of trying to pseudo manage two SUN boxes with an unknown past. I was not responsible for setting them up, anything that was done on them previously, and have no means of figuring out anything that was done to them. So far I have changed the... (4 Replies)
Discussion started by: tawnos42
4 Replies
6. AIX
:b:Hi,,
How do configure firewall in aix.. similar to linux iptable.
Rgards,
k.sumathi. (3 Replies)
Discussion started by: sumathi.k
3 Replies
7. Cybersecurity
Hey Guys,
I am looking for a good firewall software to implement in medium/large office, with at least 150 users.
I was hopping you guys could help me on this one.
Regards, (4 Replies)
Discussion started by: andrevicente
4 Replies
8. UNIX for Beginners Questions & Answers
Hi,
I want to validate ssh connection one after one for multiple servers..... password less keys already setup but now i want to validate if ssh is working fine or not...
I have .sh script like below and i have servers.txt contains all the list of servers
#/bin/bash
for host in $(cat... (3 Replies)
Discussion started by: sreeram4
3 Replies
LEARN ABOUT DEBIAN
auscope
AUSCOPE(1) General Commands Manual AUSCOPE(1)
NAME
auscope - Network Audio System Protocol Filter
SYNOPSIS
auscope [ option ] ...
DESCRIPTION
auscope is an audio protocol filter that can be used to view the network packets being sent between an audio application and an audio
server.
auscope is written in Perl, so you must have Perl installed on your machine in order to run auscope. If your Perl executable is not
installed as /usr/local/bin/perl, you should modify the first line of the auscope script to reflect the Perl executable's location. Or,
you can invoke auscope as
perl auscope [ option ] ...
assuming the Perl executable is in your path.
To operate, auscope must know the port on which it should listen for audio clients, the name of the desktop machine on which the audio
server is running and the port to use to connect to the audio server. Both the output port (server) and input port (client) are automati-
cally biased by 8000. The output port defaults to 0 and the input port defaults to 1.
ARGUMENTS
-i<input-port>
Specify the port that auscope will use to take requests from clients.
-o<output-port>
Determines the port that auscope will use to connect to the audio server.
-h<audio server name>
Determines the desktop machine name that auscope will use to find the audio server.
-v<print-level>
Determines the level of printing which auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater
output detail.
EXAMPLES
In the following example, mcxterm is the name of the desktop machine running the audio server, which is connected to the TCP/IP network
host tcphost. auscope uses the desktop machine with the -h command line option, will listen for client requests on port 8001 and connect
to the audio server on port 8000.
Ports (file descriptors) on the network host are used to read and write the audio protocol. The audio client auplay will connect to the
audio server via the TCP/IP network host tcphost and port 8001:
auscope -i1 -o0 -hmcxterm
auplay -audio tcp/tcphost:8001 dial.snd
In the following example, the auscope verbosity is increased to 1, and the audio client autool will connect to the audio server via the
network host tcphost, while displaying its graphical interface on another server labmcx:
auscope -i1 -o0 -hmcxterm -v1
autool -audio tcp/tcphost:8001 -display labmcx:0.0
SEE ALSO
nas(1), perl(1)
COPYRIGHT
Copyright 1994 Network Computing Devices, Inc.
AUTHOR
Greg Renda, Network Computing Devices, Inc.
1.9.3 AUSCOPE(1)