NI-4100 Ethernet issue

Danny Campbell

I had an interesting time today with a NI-4100 and an older Netgear 8 port 10/100 switch it was an xx-108 model).

WIth the ethernet mode set to auto, lights would blink, but no communication. Same if I tried to set it to 100 full or 100 half. Both 10 Full and 10 half worked. Everything else attached to this switch did OK with auto settings and ran fine at 100 full.

Replaced it with a newer D-Link and everything was good.

DHawthorne

I've had the exact opposite experience, where a D-Link would not allow devices to connect, but a Netgear would. I wound up sending mine to AMX, and they sent me a Netgear to replace it, saying the auto-rate algorithm in the D-Link was messing things up. I've been using Netgear exclusively since, without a problem.

Spire_Jeff

The last time this situation occured I was working in the computer and networking field. We upgraded a 10bt hub to 10/100 switch and everything stopped working. The problem came down to the contractor we used for the wiring made up his own standard for wiring and it was not pairing the wires properly. This wasn't a problem for the 10bt hub because the runs were short enough, but it would not work properly at 100bt speeds. The only thing I can think of in your situation is that maybe the new switch is better at handling errors and retransmissions than the older switch? It might also just be that the old switch is failing and the failure isn't as pronounced at 10bt speeds.

Jeff

Danny Campbell wrote:

I had an interesting time today with a NI-4100 and an older Netgear 8 port 10/100 switch it was an xx-108 model).

WIth the ethernet mode set to auto, lights would blink, but no communication. Same if I tried to set it to 100 full or 100 half. Both 10 Full and 10 half worked. Everything else attached to this switch did OK with auto settings and ran fine at 100 full.

Replaced it with a newer D-Link and everything was good.

ldeblank@jnv.nl

ethernet problems

Had this problem several times most of the time with ni-x000 controllers.
Changing ethernet mode to 10Mb half solved most of the times the problem.
I even had the problem when conecting a wap-200 with a cross cable to a controller.

Two weeks ago i spoke someone from AMX who asked me if i filed in a gateway in the controller even if the controller is stand alone.

He told me to do that becuase with the new Duet firmware the controller seems to polling for devices. Since that i fill in the gateway on a controller on my desk an tryed every day for dropping connections. I must say that in the last week it happens just once instead of several times an hour. Maybe it's a solution for you all.

Good Luck

Darkside

ldeblank@jnv.nl wrote:

Two weeks ago i spoke someone from AMX who asked me if i filed in a gateway in the controller even if the controller is stand alone.

He told me to do that becuase with the new Duet firmware the controller seems to polling for devices.

The connection/disconnection issue ldeblank@jnv.nl makes reference to is in a number of other threads in the forum already and the potential problem should not be ignored. If you are in doubt about the gateway address or simply don't have one, then you should set this field to the same address as the NetLinx controller itself.

Danny Campbell

In this case, I did have a static address, the proper subnet mask and a valid gateway address. This was one of the old Netgear switches that was back from when they still used blue painted metal cases instead of the newer plastic ones. (My newer 5-port plastic Netgear worked just fine).

10 full and 10 half both worked without any problems, but the customer was afraid that 10 wouldn't be "fast enough" so we used his new switch.