We’ve encountered persistent challenges while configuring ADTRAN devices via console access, specifically when using Windows 11 systems. Unlike traditional networking equipment, ADTRAN routers appear to require a distinct method for console access:
A USB to RS232 male converter is needed instead of a standard console cable.
When initiating remote support sessions, especially over RDP or screen sharing, a mismatch in SMB protocol handling on Windows 11 seems to disrupt the connection.
Additionally, traditional RJ-45-to-DB9 console cables are not functional in this setup.
These issues are introducing frustration into our deployment and support processes. This is why we currently recommend using Windows 10, where the legacy protocol handling appears more stable and compatible with ADTRAN’s console requirements.
We’d appreciate any insights, workarounds, or configuration tips from the community — especially from those who have managed stable ADTRAN console access under Windows 11 environments.
Hi @SarmadImdad , wanted to see if I can get you some help with this.
The very first thing I would advise is to open a case at my.adtran.com or by phone at 888-4ADTRAN. This seems like an issue that is critically impacting operations and I'd like to see it resolved. As a reminder, in-warranty Adtran hardware is eligible for phone and email support with a valid service contract (ProCare).
With that out of the way, I would like you to fill in a few details for me:
1. What Adtran hardware, specifically, seems to be affected? Since you mention RS232, I have to assume you are working with the NV3140 or TA900/900e as those are the only supported models in the portfolio with this interface today.
2. Hardware revision?
3. Which terminal emulator are you using?
4. Your statement regarding RDP is the first I've heard of this and I don't see any customer cases to indicate issues with remote support are widespread. To be clear that I am understanding this correctly...
Josh P
Senior Solutions Engineer
Adtran