|
|
| Author |
Message |
Nuldaan
Sir Postalot
Joined: 07 Nov 2002
Posts: 1179
|
 Posted: 04/19/05 - 17:34 Post subject: PCAnywhere and Port forwarding help
|
|
|
Here's the scenario:
I have a Comcast cable modem/router with a Netgear router behind it. Behind the Netgear is a computer with PCAnywhere running as a service. The Comcast router is forwarding ports 22, TCP 5631 and UDP 5632 to 10.1.10.8 (which is the Netgear's WAN IP). The Netgear is forwarding the same ports to 192.168.100.100 (which is the computer running PCAnywhere).
The security logs for both routers show the PCAnywhere log in attempts being forward properly. The logs looks like this:
Comcast:
Source: 63.204.186.94:5631 Destination: 10.1.10.8:5631
Source: 10.1.10.8:5631 Destination: 63.204.186.94:5631
Netgear:
Source: 63.204.186.94:5631 Destination: 192.168.100.100:5631
Source: 192.168.100.100:5631 Destination: 63.204.186.94: 5631
As far as I can tell, that shows both NAT and port forwarding to be functioning correctly but all PCAnywhere log-ins attempts time out. I have the firewalls on both routers set up to allow all outgoing traffic as well.
Does anyone know what could be causing the logins to fail?
|
|
|
Back to top
|
|
|
|
 |
Occulis
RealPoor Jedi
Joined: 11 Oct 2002
Posts: 13293
Location: Moral Relativity Central
|
|
Posted: 04/19/05 - 18:35 Post subject:
|
|
|
|
Try disabling all firewalls until the forwarding is working
|
|
|
Back to top
|
|
|
|
|
Finigan
RealPoor Guru
Joined: 11 Oct 2002
Posts: 3817
|
|
Posted: 04/19/05 - 19:00 Post subject:
|
|
|
PC Load Letter?
What the f**k is PC Load Letter!?!
|
|
|
Back to top
|
|
|
|
|
gotissues68
RealPoor Sensei
Joined: 21 Aug 2003
Posts: 1866
|
|
Posted: 04/19/05 - 19:27 Post subject:
|
|
|
|
go grab a packet sniffer and see if the attempt is making it to the PC. You've made it as far as the netgear, is the netgear not getting it to the PC?
|
|
|
Back to top
|
|
|
|
|
kemble
RealPoor Sensei
Joined: 14 Oct 2002
Posts: 1909
Location: MI
|
|
Posted: 04/19/05 - 20:22 Post subject:
|
|
|
|
|
|
Back to top
|
|
|
|
|
khrath
RealPoor Master of Posts
Joined: 11 Oct 2002
Posts: 8750
|
|
Posted: 04/20/05 - 02:30 Post subject: Re: PCAnywhere and Port forwarding help
|
|
|
| Nuldaan wrote: | Here's the scenario:
I have a Comcast cable modem/router with a Netgear router behind it. Behind the Netgear is a computer with PCAnywhere running as a service. The Comcast router is forwarding ports 22, TCP 5631 and UDP 5632 to 10.1.10.8 (which is the Netgear's WAN IP). The Netgear is forwarding the same ports to 192.168.100.100 (which is the computer running PCAnywhere).
The security logs for both routers show the PCAnywhere log in attempts being forward properly. The logs looks like this:
Comcast:
Source: 63.204.186.94:5631 Destination: 10.1.10.8:5631
Source: 10.1.10.8:5631 Destination: 63.204.186.94:5631
Netgear:
Source: 63.204.186.94:5631 Destination: 192.168.100.100:5631
Source: 192.168.100.100:5631 Destination: 63.204.186.94: 5631
As far as I can tell, that shows both NAT and port forwarding to be functioning correctly but all PCAnywhere log-ins attempts time out. I have the firewalls on both routers set up to allow all outgoing traffic as well.
Does anyone know what could be causing the logins to fail? |
You really should stay away from running NAT behind NAT if possible. It's bad karma.
Make sure pc anywhere is set up to accept outside connections, and make sure you dont have a software firewall blocking it also.
|
|
|
Back to top
|
|
|
|
|
gotissues68
RealPoor Sensei
Joined: 21 Aug 2003
Posts: 1866
|
|
Posted: 04/20/05 - 09:06 Post subject: Re: PCAnywhere and Port forwarding help
|
|
|
| khrath wrote: | | Nuldaan wrote: | Here's the scenario:
I have a Comcast cable modem/router with a Netgear router behind it. Behind the Netgear is a computer with PCAnywhere running as a service. The Comcast router is forwarding ports 22, TCP 5631 and UDP 5632 to 10.1.10.8 (which is the Netgear's WAN IP). The Netgear is forwarding the same ports to 192.168.100.100 (which is the computer running PCAnywhere).
The security logs for both routers show the PCAnywhere log in attempts being forward properly. The logs looks like this:
Comcast:
Source: 63.204.186.94:5631 Destination: 10.1.10.8:5631
Source: 10.1.10.8:5631 Destination: 63.204.186.94:5631
Netgear:
Source: 63.204.186.94:5631 Destination: 192.168.100.100:5631
Source: 192.168.100.100:5631 Destination: 63.204.186.94: 5631
As far as I can tell, that shows both NAT and port forwarding to be functioning correctly but all PCAnywhere log-ins attempts time out. I have the firewalls on both routers set up to allow all outgoing traffic as well.
Does anyone know what could be causing the logins to fail? |
You really should stay away from running NAT behind NAT if possible. It's bad karma.
Make sure pc anywhere is set up to accept outside connections, and make sure you dont have a software firewall blocking it also. |
You'd be amazed at the number of people I see run double NAT and I want to so badly ask them what the f**k they're thinking...
|
|
|
Back to top
|
|
|
|
|
kemble
RealPoor Sensei
Joined: 14 Oct 2002
Posts: 1909
Location: MI
|
|
Posted: 04/20/05 - 09:55 Post subject: Re: PCAnywhere and Port forwarding help
|
|
|
| gotissues68 wrote: | | khrath wrote: | | Nuldaan wrote: | Here's the scenario:
I have a Comcast cable modem/router with a Netgear router behind it. Behind the Netgear is a computer with PCAnywhere running as a service. The Comcast router is forwarding ports 22, TCP 5631 and UDP 5632 to 10.1.10.8 (which is the Netgear's WAN IP). The Netgear is forwarding the same ports to 192.168.100.100 (which is the computer running PCAnywhere).
The security logs for both routers show the PCAnywhere log in attempts being forward properly. The logs looks like this:
Comcast:
Source: 63.204.186.94:5631 Destination: 10.1.10.8:5631
Source: 10.1.10.8:5631 Destination: 63.204.186.94:5631
Netgear:
Source: 63.204.186.94:5631 Destination: 192.168.100.100:5631
Source: 192.168.100.100:5631 Destination: 63.204.186.94: 5631
As far as I can tell, that shows both NAT and port forwarding to be functioning correctly but all PCAnywhere log-ins attempts time out. I have the firewalls on both routers set up to allow all outgoing traffic as well.
Does anyone know what could be causing the logins to fail? |
You really should stay away from running NAT behind NAT if possible. It's bad karma.
Make sure pc anywhere is set up to accept outside connections, and make sure you dont have a software firewall blocking it also. |
You'd be amazed at the number of people I see run double NAT and I want to so badly ask them what the f**k they're thinking... |
You can thank the plug and play functionality that must be built into every product sold today.
|
|
|
Back to top
|
|
|
|
|
gotissues68
RealPoor Sensei
Joined: 21 Aug 2003
Posts: 1866
|
|
Posted: 04/20/05 - 10:58 Post subject: Re: PCAnywhere and Port forwarding help
|
|
|
| kemble wrote: | | gotissues68 wrote: | | khrath wrote: | | Nuldaan wrote: | Here's the scenario:
I have a Comcast cable modem/router with a Netgear router behind it. Behind the Netgear is a computer with PCAnywhere running as a service. The Comcast router is forwarding ports 22, TCP 5631 and UDP 5632 to 10.1.10.8 (which is the Netgear's WAN IP). The Netgear is forwarding the same ports to 192.168.100.100 (which is the computer running PCAnywhere).
The security logs for both routers show the PCAnywhere log in attempts being forward properly. The logs looks like this:
Comcast:
Source: 63.204.186.94:5631 Destination: 10.1.10.8:5631
Source: 10.1.10.8:5631 Destination: 63.204.186.94:5631
Netgear:
Source: 63.204.186.94:5631 Destination: 192.168.100.100:5631
Source: 192.168.100.100:5631 Destination: 63.204.186.94: 5631
As far as I can tell, that shows both NAT and port forwarding to be functioning correctly but all PCAnywhere log-ins attempts time out. I have the firewalls on both routers set up to allow all outgoing traffic as well.
Does anyone know what could be causing the logins to fail? |
You really should stay away from running NAT behind NAT if possible. It's bad karma.
Make sure pc anywhere is set up to accept outside connections, and make sure you dont have a software firewall blocking it also. |
You'd be amazed at the number of people I see run double NAT and I want to so badly ask them what the f**k they're thinking... |
You can thank the plug and play functionality that must be built into every product sold today. |
*sigh* yea.. what really kills me is when people say they are running a DSL "modem" and a Linksys "Router" ... which ok the Linksys is technically a "router" its more of a simple NAT device .. when I think router I think of something like a Cisco or Juniper or Nortel.. and its not a DSL "Modem" and never will be in fact its not really a Cable "Modem" either *sighs again*.. Modem is short for modulate, demodulate which assumes digital to analog ... DSL = Digital Subscriber Line .. its not ASL Analog subscriber line :-p lsdfkasd;lfksadl;fsadkfadsl;fkad ;flkdsaal;dskf-30ivtwpvgofejapdfgjkfdadskfjadsfdsfl;
|
|
|
Back to top
|
|
|
|
|
Nuldaan
Sir Postalot
Joined: 07 Nov 2002
Posts: 1179
|
|
Posted: 04/20/05 - 11:57 Post subject:
|
|
|
Let me guess, you work in tech support, Gotissues? NAT behind NAT works just fine as long as you take the time to configure your network properly.
The question's academic at this point anyway since the connection works fine at 64000 and 64001. Strange that it didn't seem to work on the default ports but I've had that problem with Comcast before. *shrugs*
|
|
|
Back to top
|
|
|
|
|
gotissues68
RealPoor Sensei
Joined: 21 Aug 2003
Posts: 1866
|
|
Posted: 04/21/05 - 01:08 Post subject:
|
|
|
| Nuldaan wrote: | Let me guess, you work in tech support, Gotissues? NAT behind NAT works just fine as long as you take the time to configure your network properly.
The question's academic at this point anyway since the connection works fine at 64000 and 64001. Strange that it didn't seem to work on the default ports but I've had that problem with Comcast before. *shrugs* |
I used to work tech support. Now I do ATM/Router shit and by ATM I don't mean like a cash ATM more like this kind of ATM
http://en.wikipedia.org/wiki/Asynchronous_Transfer_Mode
[edit]
btw glad you got it working =) Wonder if Comcast is blocking the ports..
|
|
|
Back to top
|
|
|
|
|
|
|
