Search the Community
Showing results for tags 'guide'.
Found 2 results
Demon27248 posted a topic in Tutorial SubmissionXLink Kai: XLink Kai is a system link tunneling application for consoles that can trick a Xbox, Xbox 360, Playstation 2, Playstation 3, PSP or Gamecube into thinking it's connected to a local area network, when actually it is connected to an international orbital server. Any System Link enabled game can then be played in this state with users all around the world. In other words, it is a global LAN network. There are 2 servers currently operating, located in Chicago & Ottawa. You can download the program from https://www.teamxlink.co.uk. Setting up your console: The best method of connecting your console to XLink is hardwiring both to your router via an ethernet cable. Another popular method is connecting your Xbox to your PC with a crossover cable, & having your PC contact your router wirelessly. View the XLink quick start guide for a full list of ways to connect your console & PC together, complete with diagrams. Using XLink Kai: Firstly, you need a Xtag, it's pretty much XLink's version of a Xbox Live "Gamertag", you can make one on the XLink Kai website. Using XLink is easy enough, there are rooms called "game arenas" for every System Link compatible game, every player in the same arena will be connected to each other & can play with each other. Simply host & join system link matches as normal when you're inside them, & you should be able to get a game started. XLink also has a private arena feature, which lets a set arena admin control who they want in the game, & can also help with bypassing orbital de-sync glitches. You can create your very own private arena by clicking the pencil icon in the Web UI. XLink also has something called "Status". This is useless now unless you want to tell other people whether your hosting a match, dedicating one, or just joining one. If you have the game "Halo 2" on Xbox, then I strongly recommend you test your XLink set up by going into the "Latin America" arena & checking if you can see & join any matches. Port Forwarding: Before you use XLink however, YOU MUST PORT FORWARD. Even if the program doesn't crash on you when you try to start it, it will be unstable as hell if you don't. There are 2 ways to port forward for XLink. The first & most easiest is called UPNP port forwarding, automatic port forwarding or dynamic port forwarding. Simply enable UPNP on your router configuration page (if it supports it), then go into the XLink Configuration menu & switch port 30000 to 0. If everything goes right, XLink should start up & in the metrics section, under port, it should have a number that is not 30000 or 0. The Newer versions of XLink have this enabled by default. If UPNP doesn't work for you, then you'll have to port forward manually. You have to set up a static IP address first http://www.howtogeek.com/howto/19249/. Next, go to your router configuration page & go to a section known as "Port Forwarding" or "Virtual Server", you can usually find it in Advanced settings. Port Forwarding is different for every router, you can find out how to port forward for yours here http://portforward.com/. There is even a step by step port forwarding guide for XLink on that site. Port Forward "30000" on "UDP" protocol. Changing Your Orbital Server: The latest version of XLink Kai (7.4.29) has a built in orb changer from the system tray, the following is for people running legacy versions or who would like to change their orbital servers manually Sometimes, the orbital servers are out of sync with each other, so you will not be able to connect to players on the orbital that the orbital you're on is out of sync to. You can fix this by switching to a different orbital server. First, close XLink Kai completely, not just the Web UI. Then, go to "Run" for Windows or "Terminal" for Mac & Linux & insert one of these commands (assuming you are on Windows 32 bit): "C:\Program Files\XLink Kai\kaiEngine.exe" --orb ADVANCED_LA "C:\Program Files\XLink Kai\kaiEngine.exe" --orb ADVANCED_QUEBEC "C:\Program Files\XLink Kai\kaiEngine.exe" --orb ADVANCED_SIXTHGENGAMING ADVANCED_LA ADVANCED_QUEBEC ADVACED_SIXTHGENGAMING Make sure you copy the whole line, not just what's in the quotation marks. If you have XLink Kai installed somewhere else, then just change the path accordingly, Windows 64 bit users will have the default installation location as: "C:\Program Files (x86)\XLink Kai\kaiEngine.exe", not "C:\Program Files\XLink Kai\kaiEngine.exe". Mac users will have XLink installed at "/Applications/kaiengine.app/Contents/MacOS/kaiengine" by default on older versions of XLink & /Applications/XLink\ Kai.app/Contents/MacOS/kaiengine from version 7.4.28 upwards. Brief Firewall Info: Certain software firewalls will block XLink Kai from running properly, these include Avast! & Zone Alarm. You can get around this by setting XLink as an exception in your software firewall's configuration menu, or disabling them while you're playing. Compatibility: The latest version of XLink fixes compatibility issues. The following only applies to version 7.4.26 & older. If you are using Windows 7, right click on Start Kai, go to properties, & make sure under compatibility, it says Windows XP Service Pack 2 (although SP3 also works for some people), for Windows 8, it must be SP3. You have to also run the program in administrator mode. Troubleshooting: First of all, make sure your console & computer are connected to each other correctly. Hardwiring both to your router is recommended. Note that most issues can often be fixed by simply cycling orbitals, restarting XLink, restarting your router & as a last resort restarting your computer. If your issue still isn't resolved after that, try the suggestions in this section of the guide Try get as many people on the same orbital as possible while playing to minimize orbital de-sync issues. : 7.4.26 & older: (If you are using Windows 7/8, make sure you have set the compatibility mode to Windows XP SP2 for 7 & SP3 for 8, & are also running XLink in administrator mode.) If everything is good with compatibility, check your port forwarding & firewalls. If everything looks okay, I recommend just doing a clean reinstall of Kai https://teamxlink.co.uk/forum/viewto...77884db6ed8a97. If the problem still occurs, it will probably be something to do with the packet capture component, switch between pdssk & winpcap in the XLink configuration menu to see if it helps. : This will usually happen if you have not port forwarded properly. It could also happen when you're using particular orbitals, in which case switching will help. If your internet "hiccups", then you will be dropped from Kai as well. : Make sure both your computer & Xbox is connected to your router via an ethernet cable (unless you are using a bridge set up with a promiscous mode network card). It could also be an issue with a firewall, or your port forwarding. Also make sure PAT is switched off in Kai's configuration menu. : Restart XLink. This is a glitch that seems to occur less in the newest version. You'll need to restart or else you won't be able to play with the person whose console you detected. : It's a firewall issue or your PC is on wireless. : The person who is not being detected by the other person leave & rejoin the room. If that doesn't work, switch orbitals. Private arenas can also help with this. : Port Forwarding or Firewall issue usually. It could also be an orbital de-sync. Both players try switching to the same orbital, if that doesn't work, restart your router & tell the player who's ping you can't see to restart his too. : Port Forwarding or Firewall issue. : This would be incredibly odd if you are using a wired connection from your Xbox to your router & your router to your PC. If you still can't see your Xbox, try entering your Xbox's MAC address into XLink's properties. Also, remember that you have to search for games to detect your console. If you're using another method, try restarting your router & if it still doesn't work, then switch into method the dual hardwire method of connection. : If everything from the above checks out, it's more than likely going to be something to do with the Mac address. On the 360 Dashboard navigate to - System Settings>Network Settings>Configure Network>Additional Settings Tab>Advanced Settings>Alternative MAC Address Use: 00125A as the first 6 digits & randomly fill in the last 6 unique digits in any combination of 0-9 or A-E with the second digit in each number pair being an even number, A,C,or, E. Example: Paired: 00 12 5A 34 78 12 As Entered On 360: 00125A347812 : Try a different orbital. What is XBSlink?: XBSlink is a program for playing system link/LAN enabled games online on various platforms, including Xbox, Xbox 360, PS2 & PS3 (It can also theoretically be used for PC games). When it comes to Original Xbox online gaming, it’s a good alternative to XLink Kai as it’s completely P2P. The program is best on Windows. Mac OSX & Linux versions exist but they require you to use MonoDevelop (see below). For more info, visit XBSlink’s website http://www.seuffert.biz/xbslink/ Download Link: The latest version of XBSlink (0.9.6.0) has a few issues establishing a connection between multiple users at a time. Version 0.9.5.3 works perfectly however, & I’ve personally never had a single issue with it. I’ve uploaded it here http://theisozone.com/downloads/misc...-version-0953/ Console Set Up: The best method of connecting your console to XBSlink is hardwiring both to your router via an ethernet cable. Another popular method is connecting your Xbox to your PC with a ethernet cable capable of doing crossover, & having your PC contact your router wirelessly. Using XBSlink: There are 2 ways to use XBSlink, direct IP address connection & ‘clouds’. Either way you need to start your engine first. Go into settings & under the ‘network’ tab, select your capture device. This is the network adapter your Xbox is connected to & in most cases should be your local area network adapter. Next, under ‘Bind to IP’, select your computer’s internal IP address. Check ‘use UPnP NAT (automatic port forwarding)’ if your router supports it, otherwise, you’ll need to manually forward port 31415 on TCP & UDP protocols. You have to set up a static IP address first http://www.howtogeek.com/howto/19249/. Next, go to the Clouds tab & change the Cloud list to ‘xbslink.baseq.fr', then hit Start Engine. Clouds: XBSlink clouds are the easiest way to play games online. Click ‘load’ (right of the cloud list url) to retrieve a list of active clouds, double click on them to join. If they require passwords, you can enter them at the bottom of the GUI. You also can create clouds this way, just enter the name of your cloud, as well as the maximum number for people you want to be able to join it & a password for it if you wish. You can also connect to other players directly via their IP address. Just enter their IP in the ‘Remote Host’ box & click ‘directly connect to remote host’. Once other users are connected to you, you should be able to see them under the ‘info’ tab. Search for system games on your console. If everything is working, you will be able to see your console’s MAC Address under ‘found devices’ at the bottom of the GUI. When other users do the same, their names will become highlighted green. Everyone you play with must have a green name AND VICE VERSA for you to be able to connect to them. Brief Firewall Info: Certain software firewalls will block XBSlink from running properly, these include Avast! & Zone Alarm. You can get around this by setting XBSlink as an exception in your software firewall's configuration menu, or disabling them while you're playing. XBSlink on OSX & Linux: XBSlink runs on Mac OSX & Linux too but you need to use MonoDevelop to use it. You can download XBSlink for your respective OS here: Now you can either install libpcap v1.1.1 http://www.tcpdump.org/ (if you don’t already have it) or edit SharpPcap.dll.config in your XBSlink directory, changing every instance of “libpcap.so.1.1.1” to your version of libpcap. You also need to download Mono Runtime & Mono Develop from here http://www.go-mono.com/mono-downloads/download.html Get the latest stable versions. To start XBSlink, you first have to open terminal & cd to the directory containing XBSlink, this is where xbslink.exe is located (type “cd [path]” e.g. “cd Users/[yourname]/Downloads/Release”). Next, type "sudo mono XBSlink.exe" into terminal & enter your admin password when it prompts you to. If everything went right, the GUI should start up & you should be able to start using XBSlink as normal now.
Basic Networking Guide: I have seen several posts on here from people who avoid FTP because they can't understand networking. I've seen advice from people who don't understand networking. I've seen people try to connect to their xbox but have no clue how. Let me explain this to you. If you don't understand, keep reading it over and over. Nobody can help you any more than this. 1. IP addressing - Your IP address is a series of numbers that gives your devices their identity on your local network. Think of it as a street address that will only mean anything to other people who live in your neighborhood. Anyone who doesn't live in your neighborhood would have absolutely no idea what it means or how to find that address. For example, here is a the most common IP scheme (subnet) in the world: 192.168.1.*. for our purposes, we're going to throw away the high level stuff about subnetting here. You'll only ever be dealing with a consumer grade network... or you'd already know this by now. For any 2 devices to communicate on your local network, they need to belong to the same subnet. This means they both need a 192.168.1.* address. (Please remember that I am trying to simplify this for the lay person.) So your pc should be for example: 192.168.1.15. Your xbox could be: 192.168.1.37. As long as they don't have the same number in the fourth slot(octet) as any other device, as long as it is >=1 and <= 254, it will be able to communicate with any other device on that same subnet. By now, you're confused.... "but he's calling the ip address range the subnet but I have another slot named subnet mask"..... 2. Subnet mask - This is a way to chop up a network(subnet) and keep certain computers from talking to other ones on a network. It was created in the early days of networking as a form of security. It's necessary to configure it for communications, but not necessary to understand it. What you need to understand is that a subnet: (for example) 192.168.1.1 Through 192.168.1.254 is a range of ip addresses. A subnet mask is what determines which IP addresses on the subnet, certain devices can communicate with. For our purposes, we're going to always set our subnet masks on all devices identically. 255.255.255.0. This allows each device to talk to each other device. Think of this as a fence... so only certain members of the neighborhood can interact with each other. 255.255.255.0 takes that fence down. (Again, I'm trying to simplify this for the lay person. If you get really into networking and realize there are subnets MUCH larger than what we're dealing with and therefore the subnet mask allows this, you may want to argue. I do this for a living and know that the description isn't dead on technically... I'm just trying to make it easy to understand.) All of our neighbors can communicate with each other. 3. Default Gateway - This is only necessary when you need communication OUTSIDE of your subnet. This is always going to be the ip address of your router. It must exist on the same subnet as the device we're trying to give access to. So for instance, your computer is 192.168.1.15 and you want to give it internet access. Your router's ip has to be 192.168.1.something.... If it's anything else your pc can't talk to it. Routers are usually the first available ip address in a subnet. It doesn't have to be this way, but that's usually the way it's set up. So, your pc so far is: IP: 192.168.1.15 Mask: 255.255.255.0 Gateway: 192.168.1.1 Think of the default gateway as the ONLY entrance and exit to the neighborhood. You can't enter or escape this neighborhood without knowing where that gateway is. 4. DNS - Dns is what translates www.whatever.com into an ip address. Your pc uses ip addresses to browse the internet. You just don't know that because we know humans don't remember numbers as well as names. The names mean something to us, so we know them and can use those. So DNS is there to make the conversion for us. This setting for primary and secondary DNS is necessary for internet access. (You need at least one to work. It's not necessary to have both as long as one works.) Google provides free public DNS you can point to, and it will work just fine. 18.104.22.168 22.214.171.124 DNS is like a phone book. You know the name of the person you're wanting to talk to, but can't remember the number. 5. Physical Connectivity - If you're relying on DHCP, both devices will have to be connected to your device that is handing out the addresses via DHCP. This can be directly or via a switch. (think of a switch as being a splitter for ethernet. It's MUCH more sophisticated than that, but for your purposes you can think of it this way.) This will handle the addressing portion as well as make the physical connection properly. You'd only have to configure your devices to use DHCP, and they will get addresses from the DHCP server and you'll be set. If you don't have a router or switch, you'll have to plug a cable directly between your two devices. Since this is an xbox group, we'll focus on cat5 cables and above. (You should be using at least cat5e in this day and age.) Network cables by default are called "straight through". What you need to know is they have 4 pairs of wires inside of them. Some are designated as send. Others receive. For the devices to communicate, one device has to have it's send connected to the other's receive... or else they won't be able to hear each other talk. Switches do this automatically. Some devices will sense this automatically and make the change on their own. This feature is called MDI/MDIX. The xbox doesn't have this feature. If your pc doesn't, you'll have to have what is called a "crossover cable". This cable simply connects send to receive so your two devices can communicate without a switch. 6. Usage - You may ask for clarification on this article, but don't ask for any more networking advice outside of this article. Everything you need is right here. If you're wanting someone to just tell you what to put into each box, ask obama. If you're not willing to do the work yourself and try to understand what you're doing... you don't belong here. If you see someone asking for networking advice in our group, send them the link to this write-up.
Board Life Status
Board startup date: April 23, 2017 12:45:48