Sponsored Content
Operating Systems SCO all tcp are CLOSED on SCO Unix on VMWARE Post 302176826 by martocapo on Wednesday 19th of March 2008 08:46:40 AM
Old 03-19-2008
all tcp are CLOSED on SCO Unix on VMWARE

Hi folks,

First of all, sorry about my english, isn't the best and thks for advance.

Here es my problem...

I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with "nmap" from a linux box to the interface of the SCO and it show me that i has all port closed except 8000 tcp, then a go to unix box and run "netstat -an|grep tcp" and show me this:

tcp 0 0 *.80 *.* LISTEN
tcp 0 0 *.* *.* CLOSED
tcp 0 0 *.22 *.* LISTEN
tcp 0 0 *.23 *.* LISTEN
tcp 0 0 *.21 *.* LISTEN
tcp 0 0 *.25 *.* LISTEN
tcp 0 0 *.110 *.* LISTEN
..... and so on..

So a realize that the problem is the "tcp 0 0 *.* CLOSED" because i do a "telnet localhost 80" or "telnet localhost 22" and it connect perfectly.
I try to see if there is a firewall running but as far as i know SCO has't firewall buildin but i trying to search an iptables or ipnat route and there isn't any, i check "netstat -rm" to check routes and is everything ok. The network interface is OK because i can connect to other linux o unix box with ssh and is works sweets.
SO if somebody can tell what is going on or give me a tips i will appreciate so much.
Cheers
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies

2. SCO

tcp port always closed in inetd

sco unix 5.0.x, several weeks ago, I add a telnet-like service in inetd.conf, it runs well for 100 network terminals. But nowdays, the terminals can connect to server successfully after booting machine, but several hours later, can not connect. "netstat -p tcp -a" can NOT find the port in... (1 Reply)
Discussion started by: shark_gao
1 Replies

3. UNIX for Dummies Questions & Answers

SCO UNIX "TCP/IP not licensed error"

I have been running 5.0.02 for more than 10 years in its present configuration. I am running a business software package on it (text based). I am trying to use my windows machines to access it through a program like "reflections" so that I can run my software from different systems but I get... (2 Replies)
Discussion started by: Parkegio
2 Replies

4. UNIX for Dummies Questions & Answers

SCO and VMware

Hello all, I'm trying to run an old SCO 5.0.4 server into VMWare workstation (and later, ESX). I've used Ghost to dump the entire image into the virtual disk, and of course it won't start since the SCSI drivers need to be replaced. Now I've tried to boot the virtual system with a generic... (13 Replies)
Discussion started by: Jeroenix
13 Replies

5. SCO

TCP in sco unix 3.2

Hi every body. I am looking for TCP package under sco unix 3.2 or sco xenix system. would you please help me? (7 Replies)
Discussion started by: javad1_maroofi
7 Replies

6. SCO

SCO TCP/IP ?

Hello! I tried to install an old version of SCO for test purposes, (3.2v4.0y), all fine, but my TCP/IP disks are "unreadable" and I cant find them on the internetz. Also, SCO doesnt respond to my request....is there any source for those images available? I have license/activation key which... (5 Replies)
Discussion started by: doc_holiday
5 Replies

7. UNIX for Advanced & Expert Users

SCO 6.0 & VMware problems

I've moved a physical server over to VMWare ESXi 5.1 using SCO 6.0 with MP4. For whatever reason, people are occasionally getting kicked out or are closing out their telnet session and it is leaving their processes running. When this happens, the sar %idle drops from 98-95% down to 25-20%. ... (1 Reply)
Discussion started by: Carlitos71
1 Replies

8. IP Networking

Need to know reason for connections closed in netstat -p tcp

Hello netstat -p give below 6634176 connections as closed.How do we trace that which all connections are being closed on the server? 1366888371 data packet headers correctly predicted 1195906 connection requests 5227320 connection accepts 5992919... (6 Replies)
Discussion started by: Vishal_dba
6 Replies

9. SCO

Configuare Network SCO UNIX 5.0.7 on Vmware

hi i installed sco unix open server 5.0.7 on virtual machine vmware and runing it, its work perfect and good. now how i can configuare network at scoadmin that i able to access nework ? ---------- Post updated at 08:56 AM ---------- Previous update was at 01:47 AM ---------- nobody can... (2 Replies)
Discussion started by: farzad226
2 Replies
SNMPNETSTAT(1)							     Net-SNMP							    SNMPNETSTAT(1)

NAME
snmpnetstat - display networking status and configuration information from a network entity via SNMP SYNOPSIS
snmpnetstat [common options] [-Ca] [-Cn] AGENT snmpnetstat [common options] [-Ci] [-Co] [-Cr] [-Cn] [-Cs] AGENT snmpnetstat [common options] [-Ci] [-Cn] [-CI interface] AGENT [interval] snmpnetstat [common options] [-Ca] [-Cn] [-Cs] [-Cp protocol] AGENT DESCRIPTION
The snmpnetstat command symbolically displays the values of various network-related information retrieved from a remote system using the SNMP protocol. There are a number of output formats, depending on the options for the information presented. The first form of the com- mand displays a list of active sockets. The second form presents the values of other network-related information according to the option selected. Using the third form, with an interval specified, snmpnetstat will continuously display the information regarding packet traffic on the configured network interfaces. The fourth form displays statistics about the named protocol. snmpnetstat will issue GETBULK requests to query for information if at least protocol version v2 is used. AGENT identifies a target SNMP agent, which is instrumented to monitor the given objects. At its simplest, the AGENT specification will consist of a hostname or an IPv4 address. In this situation, the command will attempt communication with the agent, using UDP/IPv4 to port 161 of the given target host. See snmpcmd(1) for a full list of the possible formats for AGENT. OPTIONS
The options have the following meaning: common options Please see snmpcmd(1) for a list of possible values for common options as well as their descriptions. -Ca With the default display, show the state of all sockets; normally sockets used by server processes are not shown. -Ci Show the state of all of the network interfaces. The interface display provides a table of cumulative statistics regarding pack- ets transferred, errors, and collisions. The network addresses of the interface and the maximum transmission unit (``mtu'') are also dis- played. -Co Show an abbreviated interface status, giving octets in place of packets. This is useful when enquiring virtual interfaces (such as Frame-Relay circuits) on a router. -CI interface Show information only about this interface; used with an interval as described below. -Cn Show network addresses as numbers (normally snmpnetstat interprets addresses and attempts to display them symbolically). This option may be used with any of the display formats. -Cp protocol Show statistics about protocol, which is either a well-known name for a protocol or an alias for it. Some protocol names and aliases are listed in the file /etc/protocols. A null response typically means that there are no interesting numbers to report. The pro- gram will complain if protocol is unknown or if there is no statistics routine for it. -Cs Show per-protocol statistics. When used with the -Cr option, show routing statistics instead. -Cr Show the routing tables. When -Cs is also present, show per-protocol routing statistics instead of the routing tables. -CR repeaters For GETBULK requests, repeaters specifies the max-repeaters value to use. When snmpnetstat is invoked with an interval argument, it displays a running count of statistics related to network interfaces. interval is the number of seconds between reporting of statistics. The Active Sockets Display (default) The default display, for active sockets, shows the local and remote addresses, protocol, and the internal state of the protocol. Address formats are of the form ``host.port'' or ``network.port'' if a socket's address specifies a network but no specific host address. When known, the host and network addresses are displayed symbolically according to the data bases /etc/hosts and /etc/networks, respectively. If a symbolic name for an address is unknown, or if the -Cn option is specified, the address is printed numerically, according to the address family. For more information regarding the Internet ``dot format,'' refer to inet(3N). Unspeci- fied, or ``wildcard'', addresses and ports appear as ``*''. The Interface Display The interface display provides a table of cumulative statistics regarding packets transferred, errors, and col- lisions. The net- work addresses of the interface and the maximum transmission unit (``mtu'') are also displayed. The Routing Table Display The routing table display indicates the available routes and their status. Each route consists of a destination host or network and a gateway to use in forwarding pack- ets. The flags field shows the state of the route (``U'' if ``up''), whether the route is to a gateway (``G''), whether the route was created dynamically by a redirect (``D''), and whether the route has been modified by a re- direct (``M''). Direct routes are created for each interface attached to the local host; the gateway field for such entries shows the address of the outgoing inter- face. The interface entry indicates the network interface utilized for the route. The Interface Display with an Interval When snmpnetstat is invoked with an interval argument, it displays a running count of statistics related to network interfaces. This display consists of a column for the primary interface and a column summarizing information for all interfaces. The primary inter- face may be replaced with another interface with the -CI option. The first line of each screen of information contains a summary since the system was last rebooted. Subsequent lines of output show values accumulated over the preceding interval. The Active Sockets Display for a Single Protocol When a protocol is specified with the -Cp option, the information displayed is similar to that in the default display for active sockets, except the display is limited to the given protocol. EXAMPLES
Example of using snmpnetstat to display active sockets (default): % snmpnetstat -v 2c -c public -Ca testhost Active Internet (tcp) Connections (including servers) Proto Local Address Foreign Address (state) tcp *.echo *.* LISTEN tcp *.discard *.* LISTEN tcp *.daytime *.* LISTEN tcp *.chargen *.* LISTEN tcp *.ftp *.* LISTEN tcp *.telnet *.* LISTEN tcp *.smtp *.* LISTEN ... Active Internet (udp) Connections Proto Local Address udp *.echo udp *.discard udp *.daytime udp *.chargen udp *.time ... % snmpnetstat -v 2c -c public -Ci testhost Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Queue eri0 1500 10.6.9/24 testhost 170548881 245601 687976 0 0 lo0 8232 127 localhost 7530982 0 7530982 0 0 Example of using snmpnetstat to show statistics about a specific protocol: % snmpnetstat -v 2c -c public -Cp tcp testhost Active Internet (tcp) Connections Proto Local Address Foreign Address (state) tcp *.echo *.* LISTEN tcp *.discard *.* LISTEN tcp *.daytime *.* LISTEN tcp *.chargen *.* LISTEN tcp *.ftp *.* LISTEN tcp *.telnet *.* LISTEN tcp *.smtp *.* LISTEN ... SEE ALSO
snmpcmd(1), iostat(1), vmstat(1), hosts(5), networks(5), protocols(5), services(5). BUGS
The notion of errors is ill-defined. V5.6 20 Jan 2010 SNMPNETSTAT(1)
All times are GMT -4. The time now is 08:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy