![]() ![]() ![]() Test 3 (checking whether the source of the problem stems from the router) The goal: I would like to figure out what the difference between Test 2 and Test 1) Test 2 (optional test I would greatly appreciate if you perform this test since 95% of it is for my own learning purposes since I am a noob in training. Test 1 (testing for any software conflict) This time, open both CMDs as administrator (right click on them and open as administrator) and type the following slightly different commands: Therefore, I would like you to do the following new tests (similar to the ones you did previously but with a slight variation). So apologies for that since you will need to repeat the tests (but in a modified form).Īdditionally looking back at Test 1, it did not give a positive result (but this might possibly be due to the nature of telnet it lasts very brief hence one needs to quickly enter the netstat command to obtain correct results). Therefore, in order to test whether the root of the problem stems from the router I will suggest a new test Test 3 - The Truth. Basically, Test 2 doesn't do much (or at least I can't figure out how it's results different from Test 1). Or to be more precise, I have been interpreting the results incorrectly. Secondly, I have just learned that I have been executing one of the tests wrong. Firstly, I have done slightly inefficient testing (by giving you suboptimal commands to use in CMD). This is because telnet was able to establish a connection via the loopback IP 127.0.0.1 (hence no software issue) and through your internal IP address which accesses your router (hence no router issues).Ĭlick to expand.Nah, don't worry about that, if anything, I have realized something I must apologize for: virusscan, firewall, etc), and also there isn't an issue with your router blocking RoR. On a side note, the two tests that we just performed implied that there no third party software on your PC blocking RoR (e.g. Based on the result, I can provide a permanent solution to the port problem (basically reserving yourself a static IP address from the router rather than from your PC because when it is done via your PC, there can be potential conflict ). Post back the IP address that is given in the output. (The command above will perform the "ipconfig" command (which displays very useful information about your network connections) and then search within that text for a line that contains the word "IPv4"). Just to confirm this, type the following command in CMD : While I was checking the results for Test 2, I noticed on the off chance that your assigned IP address to your PC is not actually "192.168.1.2" but rather "192.168.1.195". I believe I have found the source of the problem. ![]() Host the RoR server as usual then type the following commands:Īs applied previously, upload the results of this test and then we will proceed. (What we have just done right now is connect to your own RoR server on port 11100 via the loop IP address of 127.0.0.1 this bypasses your router and hence is used to test whether some software is preventing RoR from hosting properly).Īdditionally, we will perform another similar test to check whether your router is the source of the problem. Now type the following commands for the corresponding CMĬopy and paste the results of the 2nd CMD or take a screenshot of it and upload it. Open two instances of CMD since you will need both (place them side by side for ease of use). Additionally, type "CMD" in your search bar and run it. Now run RoR and host a multiplayer server (such that you are on the character picking screen). To enable the feature to connect to your own server, you will need to activate the "Telnet" feature:Ĭontrol Panel -> Programs -> "Turn Windows features on or off" - enable -> "Telnet Client" (No need to check "Telnet Server") In order to achieve this, you will need to connect to your own RoR server. It seems that something is blocking your RoR from being properly hosted.įirstly, let us find where the problem stems from (which most likely is either software based from your PC or potentially your router). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |