XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) (03/05/90)
Hallo, last friday, we stumbled over a very weird problem with NCSA-Telnet 2.2 from Clarkson University (tn3270 support added). We are running a local area Ethernet (yellow cable) with 7 Unix-workstations, 7 TCP/IP Terminalservers and three PC's. The PC's run tn3270 from clarkson. Two of them use a WD8003 card with NCSA build in driver, one uses a NI5010 card with the packet driver interface. Our Ethernet is connected via a Bicc-Bridge and a star-hub to the universities' backbone Ethernet. Until friday everything worked fine. Suddenly the PC's begun to complain when starting the tn3270 software: Conflict with ethernet hardware address 2:7:1:1:67:4c ERROR: The conflicting uses the same IP address Surprisingly the reported hw address was/is the address of the machine itself. This is true for all three PC's. After that message no connections were possible . On saturday I played around with this problem and I discovered, that I could stop the error by switching off either the bridge, or the star-hub. This solution is of course very unsatisfactory. I think we have a local problem, that we have to solve with the local people, but I wonder whether anybody has expired similar behaviour. It seems that tn3270 sends an arp request before it starts the server mode. This request seems to be reflected on the other side of the bridge and the PC 'sees' a packet with same IP and hw address. Is there any way to prevent this initial arp? Any help is welcome Regards Martin Knoblauch TH-Darmstadt Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt, FRG BITNET: <XBR2D96D@DDATHD21>