I have a CTX-100 with an ACTU3A processor. I am attempting to make some programming changes using the onboard NIC with WinAdmin. I have my laptop set with a static IP of 192.168.254.252. I have verified the ACTU3A IP address thru a tele set via operation 916 as 192.168.254.253. I am able to establish a link, and ping the .253 address, but when I try to use WinAdmin it can't get there. I have used WinAdmin on other CTX-100s with no problem. Anyone have any ideas? Thanks.

Try a system reboot.

If this is an ACTU3A and you really are using WinAdmin, then stop using WinAdmin. You need the proper version of (N)eManager.

Thanks Pat and Phonemeister. I have tried a hard reboot (power cycle) with no effect.
Apparently in the past I have used WinAdmin on CTX-100s, but the processors must have been an ACTU02A. How would I determine what version of eManager to use? I believe I have v5?

WinAdmin worked up to version 2.22, then they developed emanager.

An ACTU2A processor will have either 2.XX up to version 3.10. I think version 1.X was on the older ACTU1A processors.

An ACTU3A processor started with version 4.00 up to the latest version 5.20.

Emanager is backwards compatable with older versions (although I have had some issues with real old 1.0X versions), so if you have emanager version 5, you would be ok in most cases. You could have issues if the processor level is higher then the emanager version.

Thanks David, I have upgraded to eManager v5 and will be giving it a try.

I'm having the same issue. Had a donated CTX100 and can't seem to get on it either. I got the IP from the phone as 192.168.254.253 I can ping it although I DO get some packet loss. The emanager says it is not responding

It has an ACTU1A V2. I am using emanager 3.10A19.

I have had issues with older ACTU1A processors with the addon AETS NIC.

On one of them, I upgraded the firmware and was able to connect. On another, we continued to have problems even after upgrading. Packet loss when connected directly could indicated problems with the NIC.

You may have to manually set your NIC's speed to 10 mb/s as the AETS does not do fast ethernet speed.

I set my NIC to 10 full and half. I can still ping .253 but now it says no response from device. When it WAS connecting it kept looking for a non existent SES on IP .252. I scanned and There is no .252 connected. I removed the ntry from the profile but it keeps looking for it anyway.

Seems like it's looking for the Stratagy iES/ES. Check under I/O devices for that entry. But it shouldn't affect you trying to connect with eManager.

Thanks everyone that responded. I found that originally I was using eManager, not WinAdmin as I thought. I was using ver 3x. I upgraded to ver 5x and was able to connect. As it turns out, the system is running ver 4x software.