Specific key (n) on keyboard not fuctional in termianl when changing to BASH

I am trying to work in the BASH shell on a shared CentOS 7 Linux machine. I am not the admin. The default shell was set to TCSH for new users. I access it remote via ssh. When I type on my keyboard in the terminal (logged in the TCSH shell) all my keys on my keyboard function properly. If I switch my terminal from TCSH to BASH by typing bash, the n character doesn't work within the terminal prompt. For example, if I type conda, what displays in the terminal is coda as if it isn't registering. It only seems to occur when I switch to the BASH shell. I have an extra keyboard and I tried plugging that in and was unable to get the n to work as well. However, capital N still works.

I work with windows and ssh using the Windows Subsystem for Linux (Ubuntu flavor) and I use VS code as my terminal GUI. I thought that the Linux Subsystem might have something to do with it, but my admin logged onto my user using Cygwin and had similar results. Other users have had similar issues in the past on this machine but are no longer part of our group and they are hard to reach. I saw some helps online that seemed to have similar problems with specific keys not work and most indicated that an update to vi or vim was necessary. I had the admin update all packages on the CentOS machine (including vi[m]) and the problem persisted. If I open a vi or vim text and type n, the key registers. It seems to be specific to the BASH terminal.

I was informed to check for an ~/.inputrc file in my home directory but no such file exists. Since my n character doesn't function, I tested several inputs in the tcsh shell to open a clean version of bash: bash --norc, as well as env HOME=/nowhere bash. Both clean bash profiles still had similar issues with no registering n characters. Typing echo $INPUTRC in both the bash and tcsh environment gave no outputs.

I cannot figure out what might be causing this issue and any advice is appreciated. Thanks in advance.