Troubleshooting connection issues

[GtoXic]

If you are having problems connecting to x10VPN, check that your firewall isn't blocking TCP 1723. Also check in your router that Protocol ID 47 isn't blocked. If this still doesn't work, or you cannot change these settings, contact your system administrator or look around google for help.

[garrettroyce]

That fixed my problem! Thanks!

[ckster60]

I got DUN error code 619 when connecting to the ip address assiged to my account.

[CoolFinalFan]

me too! wondering ... how do check to see if TCP 1723 is open, and also, how to open up router

update: it's finally working. I just kept logging in and then it happened I'm in the VPN rite now!!

Thanks!

[ckster60]

OK, I got my connection problem fixed.

First I can not use the ip address assigned to me, through 1723 port on this ip is open, but I simply can not connect through it, I need to use the shared ip instead, but now I can connect through it. Thank you very much.

A note for those who using Windows from xp to 8:

Select pptp protocol.
Select request encryption.
Use MS-CHAP v2.

I am able to connect to vpn service by using an android ICS phone too, but only through the server address, not through the assigned ip address.

Btw, To check if port 1723 is opening, type the following in CMD widow:

telnet <insert ip here> 1723.

If it is not opened, it will shown a connection refused messages.

[garrettroyce]

I can not use the ip address assigned to me

I don't believe you "use" the assigned IP address. Everything is done through the server (using either the url or IP; I used server1.x10vpn.com in case the server IP changes). The IP assigned is what your IP address will appear as to everyone outside of your NAT/VPN/etc.

You also have to consider that there's no guarantee your assigned IP will be the same forever. X10VPN is in beta, after all and the website states the IP address is "dedicated" and does not say "static."

[ckster60]

I don't believe you "use" the assigned IP address. Everything is done through the server (using either the url or IP; I used server1.x10vpn.com in case the server IP changes). The IP assigned is what your IP address will appear as to everyone outside of your NAT/VPN/etc.

You also have to consider that there's no guarantee your assigned IP will be the same forever. X10VPN is in beta, after all and the website states the IP address is "dedicated" and does not say "static."

According to what you mentioned above, then the "dedicated" ip assigned to my account is meaningless. Btw, a good vpn provider needs to have mulitiple ip address as the access points for their clients to login through these ip address, this is to prevent a single ip address or a range of ip addresses be blocked by certain kind of firewalls. I am sure that x10 will implement such kind of strategy when this service out of beta.

I just want to point out that in the pass 2-3 hours of testing, I notice that the server ip equal to the ip assigned to my account. My windows PCs can login either through the server1.x10vpn.com and through the ip in numeric form, but my android phone can only login through server1.x10vpn.com - the domain name.

[Corey]

Hi,

You need to connect via the shared IP to login to the system. Once you login the system runs a check to see if you have a dedicated IP assigned to the account, if so, it assigns you this outbound IP address so any website you go to will see the dedicated IP.

Can you go to Google and search what is my ip? To see if your dedicated IP comes up properly?

[ckster60]

What you mean the dedicated IP is for outbound only, that makes sense. It seems the system is up and running now. I am happy to report that both my PC and my andriod phone can login through server1.x10vpn.com now. It always routes out through the ip assigned to me, but the outbound ip reverse DNS also be resolved to server1.x10vpn.com a bit confusing me at first.

[Corey]

Yeah, we'll be adding in the ability for user's to change their rDNS record if they have a dedicated IP.

Once you get connected all connections should come from your dedicated IP address even though you're connected to the shared one.