Linksys WAG54GS Port Forwarding

Hi,

I have recently splashed out on the said router and USB wireless adaptor of the same brand. Network is stable and running fine and I happy to report, which is something I guess! However, I have been scratching my head over the past week or so trying to get port forwarding work, to no avail. I have rung linksys and followed every step they suggest, and still the same result. I am assured by them that the router has the required port open and that everything is fine according to their port scanning s/w...

What I am trying to do is to create a secure tunnel from my work PC to my home PC (through company proxy) on port 443 using putty and copssh as the listener on my home box... Then use TightVNC to remote connect using this tunnel. Bascially, port forwarding a local port to 5900 remotely.

copssh is installed as a service and appears to be configured correctly, although I am unsure about how I would test this... As I said, the network is up fine and I have also been able to connect using logmein, which is ok, but pitifully slow! My n/w adapter is configured with a static IP and I have setup said IP in port range forwarding AND port range triggering on the router with no effect...

Does anyone have any pearls of wisdom (apart from buy a new router as it is not an option unfortunately!). I am pretty new to this networking lark and so I apologise in advance if I have left any vital info out... Thanks for any help!

Cheers

Tim

Reply to
timothy.hill
Loading thread data ...

I was going to write a long drawn out post to try to figure out exactly what the heck you have going on here but one question before going much further. Have you tried port forwarding something simple yet like an ftp server or something? Once you figure out of the port forwarding is actually working you can start troubleshooting the setup of this mess of stuff you have going here.

:Does anyone have any pearls of wisdom (apart from buy a new router as :it is not an option unfortunately!). I am pretty new to this networking :lark and so I apologise in advance if I have left any vital info out... :Thanks for any help! : :Cheers : :Tim

Reply to
Dave

You got the company's permission to be doing this then ask the networking people there to help you. If you don't have it, then why would you put your company's network at risk by you trying to make contact with your non secure home network that could lead to the compromise of the company's LAN?

And you got a wireless situation no less with all the security issues of wireless that can be easily hacked on your end.

What is so important at home that you would risk your company's LAN and your job and get terminated behind your activities, because the next thing you'll be into is *oh* let me start xfering things from my little networking situation from home to work?

What if *you* introduce something to the company's LAN that leads to its compromise. I'll guarantee that your little home networking situation is not secure and none of the machines on your LAN are secure and if your situations is already compromised wire or wireless you don't even know it.

The company is paying you to do your job and not to be playing network man putting the company's security at risk..

Duane

Reply to
Duane Arnold

snipped-for-privacy@gmail.com hath wroth:

Reply to
Jeff Liebermann

snipped-for-privacy@gmail.com hath wroth:

I do this all the time. It's no big deal. See:

formatting link
formatting link
've had excessive entertainment with the various 1.3 beta versions of TightVNC. 1.2.9 works, but doesn't have a file transfer feature. Recently, I've switched to RealVNC and found that it works MUCH faster.

The gotcha is forgetting to setup the Windoze Firewall Exceptions for VNC for incoming connections (if you want these). Neither VNC mutation does this. If you can't get an incoming connection, but think you've done it right, then temporarily turn off the Windoze Firewall and see if that's the problem.

Reply to
Jeff Liebermann

I hate my company. The job sucks, the company sucks and they shaft their employees completely.

Is that reason enough for you Duane?

To be honest though Duane, I care not whether I get yours or anyone elses approval - that is not what I asked for. If I had asked for that, then you would be completely justified in posting the response above. Therefore, given that you have not contributed anything useful, then I am sure you won't mind me telling to to f*ck off and keep your opinions to yourself.

TTFN

Reply to
timothy.hill

Fuck you and I hope someone empties out your bank account - you m*********er.

Duane :)

Reply to
Duane Arnold

Ah, yet another considered and intelligent reply from our Duane, the Nazi... Why are you so angry all the time Duane? Is it cos your fag of a dad isn't putting out to you anymore? Are you missing that daddy love?

Reply to
timothy.hill

Hi Dave,

Thanks for taking the time to reply... I have setup single port forwarding, port range forwarding and port range triggering for telnet (all for port 23) on my router. So then I go back to my work PC and try to telnet to my home PC and don't get anything... I have Zone Alarm (free version) as my firewall which normally tells you if something tried to access the machine and I am not getting any of this (I can see via logmein). Windows firewall is not enabled... Therefore, because Zone Alarm is not registering any access attempts, then I am inclined to think that port forwarding is failing.

Would you agree?

Reply to
timothy.hill

(Stuff)

Its better to be silent and thought a fool, then to speak and perhaps prove it. Mark McIntyre

Reply to
Mark McIntyre

Office firewall blocking telnet? Very likely in a corporate environment. I can't think of any business reason to allow telnet out, offhand. What error do you get? Connection refused or timeout?

So the traffic isn't getting as far as your PC.

Does your router perform any logging? If so, check whether its blocking anything unexpected. If you don't see anything incoming to the router, it means that for some reason your connection isn't getting routed over the internet even. In that case I'd suspect your ISP or your office firewall. Mark McIntyre

Reply to
Mark McIntyre

But my fag ass daddy bent your Ho mama's knee caps had you are you

*bastard*.

Duane :)

Reply to
K-Hen-Butt-Kicker

Back the Hell off, you know better.

Duane :)

Reply to
Duane Arnold

You insult me you SOB and you think I am going to let you slide on it, when all I was trying to do was give you was some friendly advise?

We're going to see just how sharp your *Rag* game is here partner, because I am battle harden and sharp with the game.

After all, I am an specialist -- that's Equal Opportunity Ragger.

I'll dog you out, family, house, dog, cat, car and anything else and have a little fun with the *Rag* game.

So I await your response. :)

Duane :)

Reply to
K-Hen-Butt-Kicker
[POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE]

FYI, by Godwin's Law, you have just conceded the debate. ;)

Reply to
John Navas

Actually, I think /you/ are the one who ought to know better. Perhaps you intended your remarks as a joke, or as a witty riposte to a troll, but it failed. Mark McIntyre

Reply to
Mark McIntyre

No, it didn't fail. It got the expected results.

Let us see what happens next.

Duane :)

Reply to
Duane Arnold

Since you have your port forwarding up, see if you can scan your computer using nmap or something similar. You could probably even just go to grc.com and use the shields up test to do a port scan on your computer. Do it with the firewall on and then with it off just to eliminate the possibility of it being the firewall. That should tell you whether or not your port 23 or whatever other port you have forwareded is open. : :Hi Dave, : :Thanks for taking the time to reply... I have setup single port :forwarding, port range forwarding and port range triggering for telnet :(all for port 23) on my router. So then I go back to my work PC and try :to telnet to my home PC and don't get anything... I have Zone Alarm :(free version) as my firewall which normally tells you if something :tried to access the machine and I am not getting any of this (I can see :via logmein). Windows firewall is not enabled... Therefore, because :Zone Alarm is not registering any access attempts, then I am inclined :to think that port forwarding is failing. : :Would you agree?

Reply to
Dave
[POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE]

GRC is *not* a good security resource. See

Reply to
John Navas

Why didn't you phrase it as "see my site..."?

Is this some pi**ing contest between you and Steve Gibson?

Reply to
George

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.