- Thread starter
- #21
To All...
I have my setup secure now with ssh. Its hard to show a picture using text but, here's my setup from bottom to top:
PBX
^^^
Windows PC(UWIN&SSHD)
^^^
Router with NAT to ELAN
^^^
Internet
^^^
SSH Remote PC using Putty and Procomm
You can startup the windows telnet service on XP machine, but keep the telnet port blocked on the firewall. That way you can use procomm to telnet to yourself to access the cmd version of putty for ssh, and still keep you machine from an incoming telnet session to your NIC. I usually just use putty to directly make changes to my pbx from the internet over ssh. Of course I using procomm instead for large scripts. On the elan router I have a public IP assigned, and the ssh port 22 forwarded to the XP PC with UWIN running the sshd service. I had to edit the /etc/rc file to add the line to start sshd when the pc boots up. Once you hit the the UWIN shell, you can then run your rlogin from there. I added some unix/linux scripts that execute the rlogin commands for you, so when you hit the UWIN shell you just type the name of the script and it get you in the pbx.
Having UWIN on a pc in the ELAN makes it easyer on accessing the pbx from other machines, because it keeps you from having to install UWIN when you can just run putty.
When locally, I have tried to use putty to directly rlogin to the pbx, but I run into problems with it locking up pty ports. The only way to fix a locked pty port is an INI. UWIN works flawlessly without locking up pty ports when rlogin everytime. Hope this is some more helpful tips to add to your guide.
I have my setup secure now with ssh. Its hard to show a picture using text but, here's my setup from bottom to top:
PBX
^^^
Windows PC(UWIN&SSHD)
^^^
Router with NAT to ELAN
^^^
Internet
^^^
SSH Remote PC using Putty and Procomm
You can startup the windows telnet service on XP machine, but keep the telnet port blocked on the firewall. That way you can use procomm to telnet to yourself to access the cmd version of putty for ssh, and still keep you machine from an incoming telnet session to your NIC. I usually just use putty to directly make changes to my pbx from the internet over ssh. Of course I using procomm instead for large scripts. On the elan router I have a public IP assigned, and the ssh port 22 forwarded to the XP PC with UWIN running the sshd service. I had to edit the /etc/rc file to add the line to start sshd when the pc boots up. Once you hit the the UWIN shell, you can then run your rlogin from there. I added some unix/linux scripts that execute the rlogin commands for you, so when you hit the UWIN shell you just type the name of the script and it get you in the pbx.
Having UWIN on a pc in the ELAN makes it easyer on accessing the pbx from other machines, because it keeps you from having to install UWIN when you can just run putty.
When locally, I have tried to use putty to directly rlogin to the pbx, but I run into problems with it locking up pty ports. The only way to fix a locked pty port is an INI. UWIN works flawlessly without locking up pty ports when rlogin everytime. Hope this is some more helpful tips to add to your guide.
