Sponsored Content
Operating Systems SCO all tcp are CLOSED on SCO Unix on VMWARE Post 302178892 by martocapo on Wednesday 26th of March 2008 01:58:19 PM
Old 03-26-2008
Thank you to the user jgt!!! i have manage to work!
I reinstall the networks interface and work it like a charm!! I have delete the network interfaces, exit and enter and install the interface again and it works!
Thanks to you!! Smilie
I love you all SmilieSmilie
 

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
ifup(8) 																   ifup(8)

NAME
ifup - bring a network interface up ifdown - take a network interface down SYNOPSIS
ifup [-nv] [--no-act] [--verbose] [-i FILE|--interfaces=FILE] [--allow CLASS] -a|IFACE... ifup -h|--help ifup -V|--version ifdown [-nv] [--no-act] [--verbose] [-i FILE|--interfaces=FILE] [--allow CLASS] -a|IFACE... DESCRIPTION
The ifup and ifdown commands may be used to configure (or, respectively, deconfigure) network interfaces based on interface definitions in the file /etc/network/interfaces. OPTIONS
A summary of options is included below. -a, --all If given to ifup, affect all interfaces marked auto. Interfaces are brought up in the order in which they are defined in /etc/net- work/interfaces. If given to ifdown, affect all defined interfaces. Interfaces are brought down in the order in which they are currently listed in the state file. Only interfaces defined in /etc/network/interfaces will be brought down. --force Force configuration or deconfiguration of the interface. -h, --help Show summary of options. --allow=CLASS Only allow interfaces listed in an allow-CLASS line in /etc/network/interfaces to be acted upon. -i FILE, --interfaces=FILE Read interface definitions from FILE instead of from /etc/network/interfaces. -e PATTERN, --exclude=PATTERN Exclude interfaces from the list of interfaces to operate on by the PATTERN. Notice that the PATTERN can be a full interface name or substrings that match interfaces. Users could easily have unexpected behaviour if they use a small string to do the match. -n, --no-act Don't configure any interfaces or run any "up" or "down" commands. --no-mappings Don't run any mappings. See interfaces(5) for more information about the mapping feature. -V, --version Show copyright and version information. -v, --verbose Show commands as they are executed. EXAMPLES
ifup -a Bring up all the interfaces defined with auto in /etc/network/interfaces ifup eth0 Bring up interface eth0 ifup eth0=home Bring up interface eth0 as logical interface home ifdown -a Bring down all interfaces that are currently up. NOTES
ifup and ifdown are actually the same program called by different names. The program does not configure network interfaces directly; it runs low level utilities such as ip to do its dirty work. FILES
/etc/network/interfaces definitions of network interfaces See interfaces(5) for more information. /var/run/network/ifstate current state of network interfaces KNOWN BUGS
/LIMITATIONS The program keeps records of whether network interfaces are up or down. Under exceptional circumstances these records can become inconsis- tent with the real states of the interfaces. For example, an interface that was brought up using ifup and later deconfigured using ifcon- fig will still be recorded as up. To fix this you can use the --force option to force ifup or ifdown to run configuration or deconfigura- tion commands despite what it considers the current state of the interface to be. The file /var/run/network/ifstate must be writable for ifup or ifdown to work properly. On Ubuntu the /var/run location is a temporary filesystem which is always writable and thrown away on shutdown. You can also use the --force option to run configuration or deconfigura- tion commands without updating the file. Note that the program does not run automatically: ifup alone does not bring up interfaces that appear as a result of hardware being installed and ifdown alone does not bring down interfaces that disappear as a result of hardware being removed. To automate the configura- tion of network interfaces you need to install other packages such as hotplug(8) or ifplugd(8). AUTHOR
The ifupdown suite was written by Anthony Towns <aj@azure.humbug.org.au>. SEE ALSO
interfaces(5), ip(8), ifconfig(8). IFUPDOWN
22 May 2004 ifup(8)
All times are GMT -4. The time now is 12:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy