[resolved] Connecting with SSH using a port forwarded XP

Liinux · 09-04-2005, 02:58 PM

I am currently have one Windows XP (Pro SP2) machine connected to the internet and to an OpenBSD machine using two different NICS. What I am trying to do is allowing me to log on my BSD machine using SSH, and making XP forward port 22 in order to achieve this.

I can connect to the BSD machine using the XP machine, no problems there. The BSD machine can connect to the internet fine too. Despite this I cannot make Windows forward the port correctly.

I've made windows forward ports before, in an earlier incarnation the BSD hosted an QuakeWorld server (on Win95), and that port forwarding worked fine, but now I cannot seem to make Windows forward any port at all. Time has passed since then, and during various system cleanups an "unnecessary" service might have been disabled.

I am running an apache server, so if I forwarded port 80 into oblivion, the site should be unaccessable. It keeps being accessable though, so that's why I think that port forwarding is disabled somewhere...

I've tried using the ICS port forwarding feature, and tried using NETSH directly, but still I cannot find out what's wrong. I cannot find any windows service that should be running that isn't. Does anyone have a clue?

Liinux · 09-05-2005, 10:51 PM

I might add that when I use Putty to establish a SSH tunnel, everything works fine.

Liinux · 09-06-2005, 01:48 AM

Ah, bugger.

When I return home from work, I will try NetworkActiv AUTAPF 1.0 and see if it works well. (http://www.networkactiv.com/AUTAPF.html). If it does, I'll probably mark this topic as resolved, even though Windows won't forward those port for me...

Liinux · 09-06-2005, 08:18 AM

Here's a clickable link for you, since my last one got a paranthesis on the end:
http://www.networkactiv.com/AUTAPF.html

That forwarder seems to work perfectly for me. I consider this matter resolved now. I hope that my ranting here will help others.

**johnwill** · 09-07-2005, 05:38 PM

Thanks for the reply, sorry you were posting on something none of us apparently could help you with. However, you have to admit, we listen real good!

Liinux · 09-07-2005, 05:54 PM

Obviously you made me able to fix it myself. I havn't bothered to find a solution for ages, but now as I posted here, I realised what needed to be done.

Maybe I'll post a new topic soon, if I cannot get my extra special VPN connection to work... :)

**johnwill** · 09-08-2005, 06:55 PM

How about something simple, don't throw a VPN at us!?

09-04-2005, 02:58 PM	#1 (permalink)
Liinux Registered User Join Date: Sep 2005 Posts: 6 OS: Win XP Pro SP2, OpenBSD 3.7-3.9, MS-DOS 6.22	Connecting with SSH using a port forwarded XP I am currently have one Windows XP (Pro SP2) machine connected to the internet and to an OpenBSD machine using two different NICS. What I am trying to do is allowing me to log on my BSD machine using SSH, and making XP forward port 22 in order to achieve this. I can connect to the BSD machine using the XP machine, no problems there. The BSD machine can connect to the internet fine too. Despite this I cannot make Windows forward the port correctly. I've made windows forward ports before, in an earlier incarnation the BSD hosted an QuakeWorld server (on Win95), and that port forwarding worked fine, but now I cannot seem to make Windows forward any port at all. Time has passed since then, and during various system cleanups an "unnecessary" service might have been disabled. I am running an apache server, so if I forwarded port 80 into oblivion, the site should be unaccessable. It keeps being accessable though, so that's why I think that port forwarding is disabled somewhere... I've tried using the ICS port forwarding feature, and tried using NETSH directly, but still I cannot find out what's wrong. I cannot find any windows service that should be running that isn't. Does anyone have a clue?

09-07-2005, 05:38 PM	#5 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,623 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Thanks for the reply, sorry you were posting on something none of us apparently could help you with. However, you have to admit, we listen real good! __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

09-08-2005, 06:55 PM	#7 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,623 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	How about something simple, don't throw a VPN at us!? __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

09-05-2005, 10:51 PM	#2 (permalink)
Liinux Registered User Join Date: Sep 2005 Posts: 6 OS: Win XP Pro SP2, OpenBSD 3.7-3.9, MS-DOS 6.22	I might add that when I use Putty to establish a SSH tunnel, everything works fine.

09-06-2005, 01:48 AM	#3 (permalink)
Liinux Registered User Join Date: Sep 2005 Posts: 6 OS: Win XP Pro SP2, OpenBSD 3.7-3.9, MS-DOS 6.22	Ah, bugger. When I return home from work, I will try NetworkActiv AUTAPF 1.0 and see if it works well. (http://www.networkactiv.com/AUTAPF.html). If it does, I'll probably mark this topic as resolved, even though Windows won't forward those port for me...

09-06-2005, 08:18 AM	#4 (permalink)
Liinux Registered User Join Date: Sep 2005 Posts: 6 OS: Win XP Pro SP2, OpenBSD 3.7-3.9, MS-DOS 6.22	Here's a clickable link for you, since my last one got a paranthesis on the end: http://www.networkactiv.com/AUTAPF.html That forwarder seems to work perfectly for me. I consider this matter resolved now. I hope that my ranting here will help others.

09-07-2005, 05:54 PM	#6 (permalink)
Liinux Registered User Join Date: Sep 2005 Posts: 6 OS: Win XP Pro SP2, OpenBSD 3.7-3.9, MS-DOS 6.22	Obviously you made me able to fix it myself. I havn't bothered to find a solution for ages, but now as I posted here, I realised what needed to be done. Maybe I'll post a new topic soon, if I cannot get my extra special VPN connection to work... :)