Belkin Router Weirdness--Unable to setup port forwarding

[asdf]

Trying to setup port forwarding on my Belking router. I want to be able to
use PcAnywhere. I've configured
virtual servers menu properly to forward all request on ports 5131/5132 TCP
to local IP address.
However I still can't connect from outside. I've also tried setting up RDC
and RealVNC with the same results.
Data is just not being forwarded correctly.

There is one weirdness however which I think might be the cause of the
problem. Our internal ip addressing is
of the form 192.168.2.x. However in the DMZ menu the static IP shows as
192.168.1.47 and there is no way
to change it. WAN IP shows the same 192.168.1.47 address. However shouldn't
the WAN ip address be the
address assigned to us by ISP(eg. 34.145.145.145)? Default gateway and DNS
servers which router supposedly
queries are 192.168.1.1 which is a nonexisted device as far as I understand.
However, our internet/email
connectivity is just fine. The link to a very similar router is below. If
anyone has any suggestions at all as to how
fix this problem I am all ears.

Thank you very much

http://www.amazon.com/gp/product/B0...47378-0503236?n=507846&s=electronics&v=glance

 

[Pegasus \(MVP\)]

Trying to setup port forwarding on my Belking router. I want to be able to
use PcAnywhere. I've configured
virtual servers menu properly to forward all request on ports 5131/5132 TCP
to local IP address.
However I still can't connect from outside. I've also tried setting up RDC
and RealVNC with the same results.
Data is just not being forwarded correctly.

There is one weirdness however which I think might be the cause of the
problem. Our internal ip addressing is
of the form 192.168.2.x. However in the DMZ menu the static IP shows as
192.168.1.47 and there is no way
to change it. WAN IP shows the same 192.168.1.47 address. However shouldn't
the WAN ip address be the
address assigned to us by ISP(eg. 34.145.145.145)? Default gateway and DNS
servers which router supposedly
queries are 192.168.1.1 which is a nonexisted device as far as I understand.
However, our internet/email
connectivity is just fine. The link to a very similar router is below. If
anyone has any suggestions at all as to how
fix this problem I am all ears.

Thank you very much

http://www.amazon.com/gp/product/B00008ZPJU/qid=1134191422/sr=8-2/ref=pd_bbs
_2/002-1447378-0503236?n=507846&s=electronics&v=glance

You don't need to set up a DMZ for this sort of thing -
port forwarding is sufficient.

Can you reach your WinVNC or RDC host from an inside machine?
Are your internal IP addresses fixed or dynamic?
Is your external address fixed or dynamic?
Do you have a software firewall on the PC? WinXP, Trend?
Let's have a look at one or two of your port
forwarding entries!

 

[asdf]

http://www.amazon.com/gp/product/B00008ZPJU/qid=1134191422/sr=8-2/ref=pd_bbs

You don't need to set up a DMZ for this sort of thing -
port forwarding is sufficient.

Can you reach your WinVNC or RDC host from an inside machine?
Are your internal IP addresses fixed or dynamic?
Is your external address fixed or dynamic?
Do you have a software firewall on the PC? WinXP, Trend?
Let's have a look at one or two of your port
forwarding entries!

Yes, I can reach the needed machine internally via the RDC and using
PCAnywhere.
We have dynamic internal addressing but the machine we need to access
remotely
has a static address. Our external address is dynamic now but will be static
as of middle
of next week. However, I went to www.whatismyip.com and used the results to
try and
connect to the machine. So I'm sure that I was trying to reach the correct
address.
Right now no AV or firewall software is installed on the server (2k3
enterprise).
Here is what our port forwarding entries look like:

Enable Description Inbound Port Type Private IP Address Private Port
x 5631-5632 TCP 192.168.2.101
5631-5632
x 5631-5632 UDP 192.168.2.101
5631-5632

the version of PCAnywhere is 11.

Also on a different menu WAN IP shows as 192.168.1.47 which is wrong as far
as I understand and there is no way of changing it.
Default gateway shows as 192.168.1.1. The same is for DNS Address.
I have screen capture of all screenshots if you want.

Thank you for replying

 

[Pegasus \(MVP\)]

able
http://www.amazon.com/gp/product/B00008ZPJU/qid=1134191422/sr=8-2/ref=pd_bbs

Yes, I can reach the needed machine internally via the RDC and using
PCAnywhere.
We have dynamic internal addressing but the machine we need to access
remotely
has a static address. Our external address is dynamic now but will be static
as of middle
of next week. However, I went to www.whatismyip.com and used the results to
try and
connect to the machine. So I'm sure that I was trying to reach the correct
address.
Right now no AV or firewall software is installed on the server (2k3
enterprise).
Here is what our port forwarding entries look like:

Enable Description Inbound Port Type Private IP Address Private Port
x 5631-5632 TCP 192.168.2.101
5631-5632
x 5631-5632 UDP 192.168.2.101
5631-5632

the version of PCAnywhere is 11.

Also on a different menu WAN IP shows as 192.168.1.47 which is wrong as far
as I understand and there is no way of changing it.
Default gateway shows as 192.168.1.1. The same is for DNS Address.
I have screen capture of all screenshots if you want.

Thank you for replying

I find it difficult to reconcile your workstation IP address
with your Default Gateway. I cannot solve this problem
for you but I propose this tightly defined test process:

1. Set an IP address of 192.168.1.101 for your test PC.
2. Make its Default Gateway & DNS 192.168.1.1.
3. Test if you can ping an outside address, e.g. www.google.com.
4. Install pcAnywhere on this machine.
5. Check if you can reach this machine from inside your network
with pcAnywhere. You may have to change another PC's IP
address to do this successfully.
6. Create a rule in your rounter that directs packets for
port 5631 to 192.168.1.101. Delete all other rules.
7. Check your external IP address. Let's assume it's aaa.bbb.ccc.ddd.
8. Execute this command from an external machine:
telnet aaa.bbb.ccc.ddd 5631

If this test works then you can move back to your preferred
IP addressing scheme, one step at a time. If it fails then post
again.

 

[asdf]

http://www.amazon.com/gp/product/B00008ZPJU/qid=1134191422/sr=8-2/ref=pd_bbs

I find it difficult to reconcile your workstation IP address
with your Default Gateway. I cannot solve this problem
for you but I propose this tightly defined test process:

1. Set an IP address of 192.168.1.101 for your test PC.
2. Make its Default Gateway & DNS 192.168.1.1.
3. Test if you can ping an outside address, e.g. www.google.com.
4. Install pcAnywhere on this machine.
5. Check if you can reach this machine from inside your network
with pcAnywhere. You may have to change another PC's IP
address to do this successfully.
6. Create a rule in your rounter that directs packets for
port 5631 to 192.168.1.101. Delete all other rules.
7. Check your external IP address. Let's assume it's aaa.bbb.ccc.ddd.
8. Execute this command from an external machine:
telnet aaa.bbb.ccc.ddd 5631

If this test works then you can move back to your preferred
IP addressing scheme, one step at a time. If it fails then post
again.

Sound like a plan but my only issue is with point #6.
On the router I can only change the last octet in the port forwarding
section.
so 192.168.2.x Only x can be changed. Can i still modify your plan to my
router or is there some other way of testing this whole thing.

Thank you

 

[Pegasus \(MVP\)]

setting
http://www.amazon.com/gp/product/B00008ZPJU/qid=1134191422/sr=8-2/ref=pd_bbs
Sound like a plan but my only issue is with point #6.
On the router I can only change the last octet in the port forwarding
section.
so 192.168.2.x Only x can be changed. Can i still modify your plan to my
router or is there some other way of testing this whole thing.

Thank you

Where does your router get the subnet address of 192.168.2 from?

Regardless of the answer, you can carry out the suggested test
with any subnet address, as long as you make sure that the
following addresses lie all in the same subnet:
- The pcAnywhere host PC IP address
- The internal pcAnywhere client PC IP address
- The Default Gateway and DNS addresses of the two above machines
- The internal IP address of the router
- The router's forwarding rule

 

[asdf]

192.168.2.x was the default setup on the router and i just left it to be
like this.

 

[Phillip Windell]

You kept saying that the WAN address was 192.168.1.x and the LAN was
192.168.2.x,.... This cannot be,...192.168.1.x would normally be the LAN
Address.

The WAN should be publicly routable IP# segment. If this is not the case
and it truely is 192.168.1.x,...then the ISP is running you through one of
thier own NAT-firewalls or a proxy server and it will simply be flat-out
impossible to do what you are trying to do because your "WAN Address" is
*unreachable* from the prublic Internet.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx