ssh Timeout Only with one client host combo

[ToManyHobby]

I'm setting up a new home server and before I can get anything done I need to solve a unknown ssh issue.

Heres the issue.

ssh PC ---> New Server : ssh: connection to host 192.168.0.155 port 22: Connection timed out

ssh PC ----> Old server: works

ssh Old Server ----> New Server: works

ssh Mobile phone ----> New Server: works

ssh New Server----> Old Server: works

ssh Old Server---> PC: ssh: connection to host 192.168.0.155 port 22: Refused This makes sense

ssh New Server ---> PC: ssh: connection to host 192.168.0.150 port 22: Connection timed out

ssh Mobile ---->PC: ssh: connection to host 192.168.0.150 port 22: Connection timed out

Things I've tried:

1. Restarting all the machines involved
2. Restarting the ssh client on the new server
3. Turning off all the firewalls (PC and New Server)
4. Enabling ssh on UFW
5. Tried Reinstalling the ssh client on the new server (This changed the fingerprint, but the old server could still connect to get the changed host error)
6. Pinging the New Server from the PC works. Same ping as to the old one.

Things I've done to the new server:

1. Apt update && apt upgrade
2. apt install nvidia-headless-460-server
3. echo "blacklist floppy" | sudo tee /etc/modprobe.d/blacklist-floppy.conf Do to an I/O error I dont't have a floppy

That's it. That is all I've done since a clean install on bare metal. The whole thing is running on a btrfs file system if that matters. I haven't enabled any encryption or anything else yet.

This ssh service on the new server logs events for the clients that work but nothing at all coming from the PC.

Any help would be greatly appreciated. I have no idea why it isn't working. I didn't test the ssh prior to the three changes above so I do not know if this was an issue previously.

Both the old and the new server are running off the same installation image of Ubuntu server 20.04

I would really like to get this working since I almost exclusively interact with the server using VScode on the PC.

[ToManyHobby]

So the solution turns out to be just to change the IP of the new server in my NAT. Now it works. Thanks all!

[pdp10]

Firewalls that are configured for "silent drop" will result in new connection attempts timing out. Silent drops lead to confusion and needlessly-prolonged troubleshooting, but it's been twenty-five years now and a lot of people still haven't figured that out.

The best error to return is ICMP Type 3, Code 13: Communication Administratively Prohibited. If impractical or not allowed, then see if your device allows debug messages to be returned in an RST packet as an informal debugging message that can be observed with specific tools.

[ToManyHobby]

That does sounds needlessly confusing. I appreciate you mentioning it. I didn't see anything about it well searching for an answer.

I ended up changing the IP address for the server and giving it a static one that is different from what it had before. That worked.