Sponsored Content
Full Discussion: Windows xp network problems
Special Forums Windows & DOS: Issues & Discussions Windows xp network problems Post 52388 by dkaplowitz on Thursday 17th of June 2004 08:00:42 AM
Old 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

Problems connecting Solaris 10 to network via ISP

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

Linux Network problems-Please help

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

Network Startup Problems

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

Problems with SS5 Network

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

Network Install Problems T2000

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

Troubleshooting Solairs 10 Network problems

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

network problems with 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

Problems with network card in 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

Vmware 7 unixware 7.13 network problems

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

How to demonstrate network problems?

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
niffconfig(8)						      System Manager's Manual						     niffconfig(8)

NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF) SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...] OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options. Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame- ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout). Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout). DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter- faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command. Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified. EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0 SEE ALSO
Daemons: niffd(8) Information: EVM(5), nifftmt(7) niffconfig(8)
All times are GMT -4. The time now is 10:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy