02-27-2006
Did you find what was wrong ?
What's your environment ? Is this box connected to a switch ? Does the box have more than one ethernet port ? [If so, are both connected ?]
I agree that any physical problem is more likely to be a cable (or part thereof) but the "send OK, Receive BAD" part of this problem may be pointing to something else as a cause.
There is a slim chance, if this is a SPARC conected to a Cisco switch, that this *might* be an auto-negotiation problem. But they fixed all that a while back, and I know nowhere near enough 'data' to make THAT kind of assumption.
====
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey,
Just need a little help I'm not sure wat I should do.
We have several little networks setup for testing different things. One of these networks we need to have running at full dulpex.
Right now we run 2 hubs (to go off to 2 differnt parts) and they are half dulpex hubs.
Is is... (1 Reply)
Discussion started by: merlin
1 Replies
2. Linux
I'm working on my homework to write a chatroom program. Different users can be on-line at the same and talk to each other.
I found that each time I invoked the accept function. A new socket was created. I don't how can I receive message from the client who is already on-line and send it to others.... (0 Replies)
Discussion started by: niukun
0 Replies
3. UNIX for Dummies Questions & Answers
This is my first attempt in installing a netbsd ever. I'm trying to get myself familiar with some commands and how things work in unix and so far i never knew its this fun. Anyway, unix is our elective here in school and school is gonna start 2 weeks. I'm just trying to get a headstart on this :D... (2 Replies)
Discussion started by: 3rr0r_3rr0r
2 Replies
4. UNIX for Dummies Questions & Answers
1) how do i know my NIC speed if its 10//100???
2)how do i setup by NIC to full duplex
3) any help on setting up etherchannel for NIC failover (1 Reply)
Discussion started by: karthikosu
1 Replies
5. Solaris
I am new to Solaris and have been searching around for this answer and I think I figured it out but I wanted to run it by you folks. I was trying to figure out if the network on this Solaris 10 machine was set up for 100 Full Duplex. I think from this output that it is 100 full duplex, am I... (2 Replies)
Discussion started by: scotbuff
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have a linux machine connected to 2 networks, with devices eth0 and eth1.
When I give the command host whatever, how do I now which network is searched for the DNS's ? Is there a default ethernet device for network related commands ? How do I change it ? :confused: (2 Replies)
Discussion started by: mik
2 Replies
7. IP Networking
Hi here is my question;
any help would be appreciated
The Linux system pokey has two Ethernet cards. The first Ethernet card is connected to a companywide
TCP/IP network covering the addresses 87.65.43.xx, where pokey's address is
87.65.43.21. The second Ethernet interface is connected to a... (2 Replies)
Discussion started by: scofiled83
2 Replies
8. IP Networking
Folks;
I have 2 SUSE servers similar in all configuration & both on the same network
(192.168.151.10 & 192.168.151.11) with the same default gateway of 192.168.151.1 and the same netmask of 255.255.255.0 and the same firewall configuration
the first one works fine and i can ssh to it & i can... (3 Replies)
Discussion started by: Katkota
3 Replies
9. Linux
hi all, im linux nubie n want to ask,
1. how to access the windows pc?
if from windows to windows, we can use :
start-run-\\192.168.1.1\e$
now, how about from linux (fedora) n want to access to windows drive?
if I use ssh from linux to windows,
ssh 192.168.6.171
ssh: connect... (6 Replies)
Discussion started by: busoh.sensen
6 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I am on Redhat 5. on the /etc/sysconfig/network file
I don't see GATEWAY as one line. I also checked /etc/sysconfig/network-scripts/ifcfg-eth0. I don't see GATEWAY.
But on the server. But when I do netstat -rn. I see many address. Is there some other settings ?
... (2 Replies)
Discussion started by: samnyc
2 Replies
TIMED(8) System Manager's Manual TIMED(8)
NAME
timed - time server daemon
SYNOPSIS
timed [ -t ] [ -M ] [ -n network ] [ -i network ]
DESCRIPTION
Timed is the time server daemon and is normally invoked at boot time from the rc(8) file. It synchronizes the host's time with the time of
other machines in a local area network running timed(8). These time servers will slow down the clocks of some machines and speed up the
clocks of others to bring them to the average network time. The average network time is computed from measurements of clock differences
using the ICMP timestamp request message.
The service provided by timed is based on a master-slave scheme. When timed(8) is started on a machine, it asks the master for the net-
work time and sets the host's clock to that time. After that, it accepts synchronization messages periodically sent by the master and
calls adjtime(2) to perform the needed corrections on the host's clock.
It also communicates with date(1) in order to set the date globally, and with timedc(8), a timed control program. If the machine running
the master crashes, then the slaves will elect a new master from among slaves running with the -M flag. A timed running without the -M
flag will remain a slave. The -t flag enables timed to trace the messages it receives in the file /usr/adm/timed.log. Tracing can be
turned on or off by the program timedc(8). Timed normally checks for a master time server on each network to which it is connected, except
as modified by the options described below. It will request synchronization service from the first master server located. If permitted by
the -M flag, it will provide synchronization service on any attached networks on which no current master server was detected. Such a
server propagates the time computed by the top-level master. The -n flag, followed by the name of a network which the host is connected to
(see networks(5)), overrides the default choice of the network addresses made by the program. Each time the -n flag appears, that network
name is added to a list of valid networks. All other networks are ignored. The -i flag, followed by the name of a network to which the
host is connected (see networks(5)), overrides the default choice of the network addresses made by the program. Each time the -i flag
appears, that network name is added to a list of networks to ignore. All other networks are used by the time daemon. The -n and -i flags
are meaningless if used together.
FILES
/usr/adm/timed.log tracing file for timed
/usr/adm/timed.masterlog log file for master timed
SEE ALSO
date(1), adjtime(2), gettimeofday(2), icmp(4P), timedc(8),
TSP: The Time Synchronization Protocol for UNIX 4.3BSD, R. Gusella and S. Zatti
4.3 Berkeley Distribution November 17, 1996 TIMED(8)