Error 302: Cannot connect to xlink kai servers

Kai Beginner Joined: 22 Jun 2014 Posts: 4

1) Before setting a static IP and port-forwarding I can start up xlink kai fine by using a wireless connection to my router.

2) After port-forwarding and setting a static IP on my mac, xlink kai (the latest version) no longer starts up. I receive "error 302: cannot connect to xlink kai servers" and then the program shuts down. This occurs even though I can still surf the web. The same error occurs whether I use a wireless or a direct connection to my router.

Please help me! Thank you for your time!

Kai Regular Joined: 02 Jan 2006 Posts: 172

Enable UPnP on your router and then try changing kai port number to 0 in your Kai Config.

Kai Beginner Joined: 22 Jun 2014 Posts: 4

Thanks for replying.

When changing the kai port to "0," after saving it reverts back to "undefined."

UPNP is enabled on my router.

The error message 302 - Cannot connect to xlink servers - is still occurring.

Kai Regular Joined: 02 Jan 2006 Posts: 172

In your kai config, is port "undefined" ??
If yes, take the screenshot of Network Settings in your Kai Config.

Posted: Sun Jun 22, 2014 11:19 pm

The deep port was removed as it wasn't been used, it's safe to ignore it and focus on the Kai port instead.

Kai Beginner Joined: 22 Jun 2014 Posts: 4

Setting port to zero like you provided ended up allowing me into xlink kai once or twice before getting the same error again. This brief access occurred with my static ip/port-forwarded wireless connection to my router. The direct connection continued to result in the error.

A moderator that I spoke with suggested that there may be a problem with my lan card software and that I should reinstall it.

Any more suggestions? Firewall is turned off and there is no anti-virus software running on my Macbook Pro. My setup consists of a router that plugged into the wall (no modem) and my Macbook Pro.

Could this problem be caused because I have both UPNP checked and have manually port-forwarded to 30,000 inside my Netgear router?

The help so far has been really appreciated.

Team XLink Administrator Joined: 17 Dec 2007 Posts: 844

This 302 error occurred because Xlink Kai cannot see his LAN card on his mac
book. After he switched to wireless i had him go to configuration and only
his wireless card was able to be seen by xlink. The only way he would be
able to connect via Ethernet cable at this point would either be to try an
updated driver for his LAN or use a USB LAN port add-on.

Edit: I was under the impression you got it working with wireless after we
talked. I saw you had made a post in general chat??

Kai Beginner Joined: 22 Jun 2014 Posts: 4

[1up]Stickey wrote:

This 302 error occurred because Xlink Kai cannot see his LAN card on his mac
book. After he switched to wireless i had him go to configuration and only
his wireless card was able to be seen by xlink. The only way he would be
able to connect via Ethernet cable at this point would either be to try an
updated driver for his LAN or use a USB LAN port add-on.

The only problem is that the 302 error is still persisting even with using a wireless/static/port-forwarded connection to my router.

Kai Regular Joined: 02 Jan 2006 Posts: 172

I have two suggestions.

1. Can your router assign the IP address dynamically to your OS X? If yes, try using DHCP.

2. Try disabling IPv6 on your OS X.

p.s.
What version is your OS X?

Team XLink Administrator Joined: 17 Dec 2007 Posts: 844

Does it work without setting a static IP and port forwarding on wireless?

Posted: Mon Jun 23, 2014 3:26 am

Typically Netgear routers have LAN DHCP locks in them now which lets you bind an IPv4 address to a specific MAC address, normally this is in the setup menu under LAN.

Also as long as your router supports UPnP you don't need to set a static IP or port forward even if you have port 30000 set as your PC/laptop will make a request to forward an action though it and your router will either choose to accept or deny the request.

If it's any help I currently have a Netgear D6300 AC router and can use XLink on any port I choose given it's not being used by something else already.