darkoperator / darkoperator/Posh-SSH
Cisco CBS350 connection timesout
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
Trying to connect to a Cisco CBS350 produces the following:
PS C:\> New-SSHSession 172.20.0.76
cmdlet New-SSHSession at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
Credential
User: user
Password for user user: ********
New-SSHSession: Session operation has timed out
[16.642s] [16:12:04]
PS C:\>
I get this no matter how long I set the timeout for. The connection works using OpenSSH or PuTTy.
I'm aware I need to use streams with Cisco switches, but I can't even get the session to establish to use a stream.
Any suggestions?
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the New-SSHSession command against a Cisco CBS350, using the timeout settings described in the issue. Compare the failing Posh-SSH connection with the working OpenSSH or PuTTY connection, then verify that a Posh-SSH session can be established before streams are used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100