Wireless Access

DTC16TN was working fine. Changed system IP address, DTC IP address, and made corresponding change to "Default Destination", but DTC port will not connect. Can ping the DTC from the HP, and can access the HP using a PC with the DTC's IP address (DTC was disabled for this test) plugged into the same switch port as the DTC. There is no routing involved, HP and DTC plugged into the same switch and are on the same network.

Checked all the global default parameters, and deleted and re-added the DTC from scratch in dtcconfig, but still no luck. The DTC resets fine, both soft and power reset.

Just keep getting "Can't establish the connection (DTC 01)" error.

Other users can telnet to the system with no problem.

Any ideas?

Does the firmware get loaded into the DTC ok?

You made need to do a "dtcconfig", delete the DTC, and re-add it.

I've had similar problems when moving one DTC from one host to another. Ended up deleting and re-adding.

HTH

-- Rod Hills

Yes, the DTC uploads its config just fine. Status LED's cycle and stabilize correctly.

Linkloop of it's MAC address returns OK.

We can ping it's new IP address, and can't ping it if it's unplugged from the network, so no duplicate IP issues.

We tried deleteing and re-adding in dtcconfig but it made no difference.

Did you try "telnet dtc port#" to connect to the port from the host side?

What does "dtctest -p" return for a port?

All your ports are terminal? You tried different ports?

Could another HPUX host on your LAN be sending the firmware down?

Could the serial cable you are using from the terminal to the DTC port be bad?

You might have to connect a terminal to the console port to do further diagnostics.

-- Rod Hills

Not sure what the telnet port#'s are. I've tried this with the DTC in question and also on another system with a known working DTC using "telnet dtc1 2100", "telnet dtc1 3100" and "telnet dtc1 1" and get "telnet connection refused" in all cases.

The "dtclist -p dtc1" returns "no events".

The "dtclist -d dtc1" event logs show download successful and all ports with a "1" status.

As far as the cable goes, don't see how that could be the problem because I'm seeing the "can't connect" message from the dtc. If the cable was bad I shouldn't be seeing anyting. Right? Also, the cable would have had to go bad at the very instant I changed the IP addresses. It was working perfectly before, so doesn't seem likely.

All ports are "terminal" ports.

Tried a different port, but get the same error message.

There is no other HP on the network.