Test Port Fowarding Failure

[gdkinsman]

It says to validate my routure settings.

My Linksys E4200V2 using ciscoconnectcloud.com to access settings:
Single Port Fowarding (also tried Port Range Forwarding)...
Application Name: CDataService
External Port: 5832
Internal Port:P 5832
Protocol: TCP
Device IP#: 192.168.1.13
Enabled: True

The good new is that the Companion on my iPhone4s is working, although I haven't tried to do anything but browse around so far.

[Motz]

I believe the e4200 has a built in firewall you need to configure. Take a look at this guide:
http://portforward.com/english/routers/ ... tguide.htm

The info you entered though for it looks good as long as 192.168.1.13 is the IP of the HTPC.

[gdkinsman]

I looked over the link you sent. Didn't see anything enlighening. Since Cisco now has a new interface (Linksys Smart Wi-FI via ciscoconnectcloud.com) and this is not my area of expertise, I could easily be missing something here. In case it's helpful, here are my settings from the Security window:

Firewall
IPv4 SPI firewall protection Enabled
IPv6 SPI firewall protection Enabled

VPN Passthrough
IPSec Passthrough Enabled
PPTP Passthrough Enabled
L2TP Passthrough Enabled

Internet filters
Enabled Filter anonymous Internet requests
Disabled Filter multicast
Disabled Filter Internet NAT redirection
Enabled Filter ident (Port 113)

DMZ
DMZ: OFF

Apps and Gaming

DDNS
Select a provider: Disabled

Port Range Forwarding

Application name Start ~ End Port Protocol Device IP# Enabled
CDataService 5832 - 5832 TCP 192.168.1.13 TRUE

I did find it interesting that I've been able to use the Companion with my extender and everything that I've tried has worked so far, except I cannot remove existing Series. I can edit them though.

I use ESET Smart Security, but have disabled it temporarily while testing. Didn't help any.

[STC]

This may help you

http://www6.nohold.net/Cisco2/ukp.aspx? ... leid=25787

[Motz]

I did find it interesting that I've been able to use the Companion with my extender and everything that I've tried has worked so far, except I cannot remove existing Series. I can edit them though.

In this area on iOS you swipe to delete on the series (also you can do this on the PCs). On android you just long press on the series to delete.

[gdkinsman]

The only differenct between STC's link's recommendation and my settings was the Protocol was set to 'Both' instead of 'TCP'. I'm afraid neither work. Are we running out of ideas yet?

[Motz]

So a few other things.

1.) We are going to be enabling Automatic UPnP port forwarding in an upcoming build of the services (off by default, and user can turn it on) so maybe that will fix it up.
2.) Double check your IP address that the ceton companion http://checkip.dyndns.com/
3.) Instead of doing portforwarding try to do port triggering to see if it likes it better. (TCP is the only thing needed either way)

ALso can you make sure the router has the latest firmware on it.

[gdkinsman]

UPnP was already enabled.

Tried port triggering, no go.

Checked router and it's on the latest software.

I tried the checkip link, but it displayed IE's cant' connect message. Will have to try again tonight.

[Motz]

You can also check: http://myip.cetoncorp.com/ (same as the dyndns.com)

If that can't detect your external Ip this might be leading us somewhere

[gdkinsman]

I was finally able to get the link to return the ip address and it matches the external ip address within the Companion interface.

[gdkinsman]

Anything new to try tonight?

[gdkinsman]

In the Companion Configuration under Network discovery, my internal ip address displays 192.168.1.100, whereas in your documentation, it shows 192.168.1.13. Is that OK?

[Cup]

Well, I'd say that there's your problem.

Any IP address(es) and hostname(s) in the documentation are examples. You need to substitute your actual information there.

So, if your HTPC's IP address is, in fact, 192.168.1.100 (verify this from the network adapter's Properties sheet in Control Panel; or, just run ipconfig at a command prompt), then that's the IP address that you'll need to use when you set up your port forwarding.

[Motz]

Yeah basically what cup says.

192.168.1.13 is an example... so if 192.168.1.100 is the IP this is the IP that you would enter on the router:
Application Name: CDataService
External Port: 5832
Internal Port:P 5832
Protocol: TCP
Device IP#: 192.168.1.100
Enabled: True

[gdkinsman]

I went into Connections under Control Panel\Network and Internet\Network and Sharing Center and clicked on Details:

Connection-specific DNS Suffix: hsd1.ca.comcast.net
Description: Intel(R) 82566DC-2 Gigabit Network Connection
Physical Address: ‎00-1E-C9-55-1B-14
DHCP Enabled: Yes
IPv4 Address: 192.168.1.100
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: Friday, October 19, 2012 12:49:11 AM
Lease Expires: Saturday, October 20, 2012 12:49:11 AM
IPv4 Default Gateway: 192.168.1.1
IPv4 DHCP Server: 192.168.1.1
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes
Link-local IPv6 Address: fe80::21ae:a3c1:104d:d731%10
IPv6 Default Gateway:
IPv6 DNS Server:

Looks like IPv4 Address matches what I have in Companion Configuration under Network discovery, internal ip address. It's not an editable field in Companion anyway, so I don't have any direct control over it. So if that is correct, I'm still in limbo...

[gdkinsman]

Oops, I didn't read your second part. I shouldn't be working on the computer after midnight. I was taking the instructions far too literally. That solves that probem.

Should the external ip port number be 5832 or 0?

[Motz]

5832:

Inside the config if you set it to 0 it will match your internal port.

So the idea here is this:
1.) Internal port: this is the port that the companion services are listening on.
2.) External port: this is the port that your router is basically listening on. So when the app tries to communicate on this port basically the router will forward from the external port to the internal port of the ip that you set for your htpc.


They can be the same or different, but you just have to set them correct and specify them in the app and the config.

[gdkinsman]

I appear to have everything working now. Next step is to give the Companion a complete test drive, both here and from afar.

Thanks for all your help.