06-17-2004
How did you determine these 4 PCs were the culprits? You had to scan the network for traffic to do so. What kind of traffic were these machines spewing?
Plus I'm assuming you took them all offline and are troubleshooting them and reintroducing them to the network one at a time with careful monitoring, right?
10 More Discussions You Might Find Interesting
1. Solaris
I have just installed Solaris 10 (x86) on my PC, which is connected to an ISP via a Netgear DG834G firewall/modem router. I can't find the network. My router has the IP address 192.168.0.1 and my ISP assigned IP address is 214.159.X.Y
I have edited various files based upon information I have... (7 Replies)
Discussion started by: christian_hicks
7 Replies
2. SuSE
Hullo everyone,
I have recently installed SUSE 9.1 and attached it to my Network router (Actiontec 54Mbps Wireless DSL Gateway) but can't connect to the internet. It comes up with the following error message:
An error occurred while loading "http://www.yahoo.com":Timeout on server - connection... (2 Replies)
Discussion started by: sybella1
2 Replies
3. Slackware
I recently installed slackware 11 and have been very happy with it until I found out that some gnome related apps can cause gnome's network manager to alter the rc.init1 script by adding 3 lines to the script containing only the command, eth_up. This causes the script not to run properly and not... (1 Reply)
Discussion started by: djtrippin
1 Replies
4. Solaris
Hey. i have a SPARCstation 5 running solaris 8 and CDE,
i know this hardware is really old but its the only Solaris machine i can afford at this time, (Student) but im having a hard time getting it on the internet, im using a cable modem, andt DHCP IPv4, but i can`t get a connection, i have heard... (0 Replies)
Discussion started by: mads-nielsen
0 Replies
5. Solaris
Hi
I am trying to do a network install of Solaris 10 08_07 onto a Sunfire T2000. I have configured all my network-boot-arguments on the client server (named sundb1). I have installed my image of Solaris on my install server (sun1).
But when I try to install using
# boot net -s
I get the... (0 Replies)
Discussion started by: Bobby76
0 Replies
6. Solaris
recently I've setup a Solaris 10 box & am having network disruption, e.g. disconnects, interrupted pings, etc) when I
connect to it from another machine, how should I troubleshoot this !
The machine is a x86 box with 3 NICs (Differnet providors). The Current NIC is a Intel Gigabit, which is... (4 Replies)
Discussion started by: stevie_velvet
4 Replies
7. SCO
SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that.
thanks (8 Replies)
Discussion started by: ajantha
8 Replies
8. SCO
hello, i am new to unix and need support</SPAN></SPAN>
</SPAN></SPAN>The problem is:
I have a SCO 5.0.5 server, and has no local network access, I think my problem are the drivers for network card.
my network card is Kingston EtheRx PCI Fast Ethernet Adapter KNE120TX and already installed the... (9 Replies)
Discussion started by: daniel_cie
9 Replies
9. UNIX for Advanced & Expert Users
i need help, i will always accord mine if my scope allows me, help me in this one..
am running vmware 7.0 in winserver 2008 on a cq61-425el, my network driver is installed correctly. and my vmware network drivers have added as well (in the device manager section).
During installation i wasnt... (0 Replies)
Discussion started by: baitz
0 Replies
10. Shell Programming and Scripting
Hi,
I work on several Sun servers running Solaris (SunOS 5.10). All of these are Application Servers with a propietary software running on it.
It happens that some times (not regularly/deterministic and not so often, i.e. twice a month circa) we register what I think are network problems.
I say... (4 Replies)
Discussion started by: Evan
4 Replies
LEARN ABOUT DEBIAN
queue-repair
queue-repair(8) System Manager's Manual queue-repair(8)
NAME
queue-repair - deal with the qmail queue directory structure
SYNOPSIS
queue-repair [ -htrcbn ] [ -n split ] [ conf-qmail ]
DESCRIPTION
queue-repair deals with the qmail queue structure; it can create a new queue, move and properly rename a queue, dynamically change the
conf-split value, convert big-todo queues to non-big-todo and vice versa, and repair a corrupted queue.
conf-qmail defaults to /var/lib/qmail/ on Debian.
OPTIONS
-h|--help
Display usage information and built-in defaults, then exit.
-t|--test
Run in test-only mode. queue-repair will attempt to report all problems that it finds, without correcting them. This is the
default.
-r|--repair
Run in repair mode. queue-repair will attempt to correct all problems that it finds, except if the basic queue directories (queue,
queue/mess, queue/info, etc) are not found.
-c|--create
Run in create-and-repair mode. queue-repair will attempt to correct all problems that it finds, including creation of a new queue
structure from scratch.
-s|--split split
Specify split as the value of conf-split. This is the number of split subdirectories for those queue directories which are hashed.
The default for qmail is 23. Appropriate values depend on the volume of mail handled, OS filesystem efficiency, and other factors,
but this should always be a prime number.
If you do not specify conf-split, queue-repair will attempt to determine the current value from the existing queue. This option can
be used, however, to change the conf-split value of an existing queue (qmail will still have to be recompiled with the new value).
When creating a new queue, this option must always be specified.
-b|--bigtoto
Use big-todo. queue-repair should be able to automatically determine if you're using qmail patched with the big-todo patch. This
option can be used, however, to convert a non-big-todo queue to a big-todo queue (qmail will still have to be recompiled with the
big-todo patch).
If neither this option nor --no-bigtodo is used, queue-repair will attempt to determine this automatically. When creating a new
queue, either this option or --no-bigtodo must always be specified.
-n|--no-bigtodo
Do not use big-todo. queue-repair should be able to automatically determine if you're using qmail patched with the big-todo patch.
This option can be used, however, to convert a big-todo queue to a non big-todo queue (qmail will still have to be recompiled with-
out the big-todo patch).
If neither this option nor --bigtodo is used, queue-repair will attempt to determine this automatically. When creating a new queue,
either this option or --bigtodo must always be specified.
--i-want-a-broken-conf-split
Force the use of a non-prime value for conf-split.
SEE ALSO
qmail(7)
queue-repair(8)