Thanks for the response, I should probably have updated this thread that I've found a workaround for this issue in the meantime.
Basically, I believe this could be a Perforce specific issue, so unless you can log into Perforce on your end, sample code alone will not be able to reproduce this. I have since found an alternative way to log into Perforce so I'm no longer looking for a solution.
I'm still unsure and curious though why Perforce rejected the login attempts in the first place. It seems like it should work since I'm sending the exact sequence of packets that Putty does. To verify this I added some debugging code into SSH.Net that outputs similar packet info as we see from Putty above, and it looks practically identical.
Basically, I believe this could be a Perforce specific issue, so unless you can log into Perforce on your end, sample code alone will not be able to reproduce this. I have since found an alternative way to log into Perforce so I'm no longer looking for a solution.
I'm still unsure and curious though why Perforce rejected the login attempts in the first place. It seems like it should work since I'm sending the exact sequence of packets that Putty does. To verify this I added some debugging code into SSH.Net that outputs similar packet info as we see from Putty above, and it looks practically identical.