Varien_Dathemire
-
Posts
14 -
Joined
-
Last visited
Posts posted by Varien_Dathemire
-
-
I've followed everything you've said, My Port list says 25565-25565 TCP 192.168.0.2 N/A N/A
I visited http://www.canyouseeme.org/ Entered 25565, and it said this:
Error: I could not see your service on 71.35.231.21 on port (25565)
Reason: Connection timed out
-
Okay, as is, Localhost and 192.168.0.2 both work, What do I do from here to make it available so that other people can join from a different computer, because that's a majority of my concern at this point. I attempted to sign in via my current IP, but it doesn't register the server.
-
Okay, I've followed each step, but the situation really hasn't changed, checking ipchicken.com again, I input the IP as it would be followed be :25565 as usual, and it says "Can't reach server" like usual. Same is said when localhost is used, but again when 192.168.0.2 is used it operates correctly.
-
At About 3:00 PM Tomorrow? Which is actually 1:00 PM for me, Yeah, I should be around. Not exactly sure what TeamViewer is, but Any and all Help I can get on this subject is greatly appreciated.
-
You could make the assumption, but its incorrect. I changed the Port, as you said I should, yet it still doesn't work. This is why I'm posting the issue on the Forums, I'm genuinely Stumped as to why it won't work, I've tried multiple means of getting it to work, Three Different Port configurations, I've fiddled with the Server Properties IP setting, but nothing is working.
-
@AlienX
When done, it responds in the same way it did previously, Localhost doesn't work, the Ip received by looking it up doesn't work, and only 192.168.0.2 Works for connection.
This is strange too because 2.1.1 was run exactly how it's shown in the Image, and I've had as much as Twelve people online at once, so the router must have been acting of its own will since I haven't changed anything until now.
@Wendo, I wasn't aware that it didn't need one, the sources I read off of at the time stated that it needed the IP to be input into it otherwise it remained impossible to connect to other than localhost, due to it not having something defined for it to be connected to.
I'd prefer to avoid Turning it off, but I wouldn't know how to open a Port within the firewall either, so I'm at a Blockade of a sort.
-
Accidental Double Post apparently.
-
@AlienX I've attached a Few Pictures, One of the Port Forwarding Page, with little Notes added, and a second one just detailing the Localhost versus 192.168.0.2 IP use.
@Wendo, I'm afraid I don't quite understand what you mean with it Binding to local interfaces, does this mean its almost automatic in its setup, so long as its not restricted by say the Firewall?
Then This I don't quite understand Either, as I'm not too familiar with how its set up, does this prevent someone from say, a town over from logging in? They obviously wouldn't be on the same machine, and I want to keep it public for my friends.
To my knowledge, no, or at least not in any way that it would impede with the Launcher, most of its settings are tuned down to a low degree. My uncle, who has an exceedingly large amount of knowledge as to how computers work, did some tuning to the firewall when I was first trying to get it to work correctly, since at the time it was actually having problems with the Firewall preventing people from connecting.Do you have windows firewall turned on? -
@AlienX I've attached a Few Pictures, One of the Port Forwarding Page, with little Notes added, and a second one just detailing the Localhost versus 192.168.0.2 IP use.
@Wendo, I'm afraid I don't quite understand what you mean with it Binding to local interfaces, does this mean its almost automatic in its setup, so long as its not restricted by say the Firewall?
Then
This I don't quite understand Either, as I'm not too familiar with how its set up, does this prevent someone from say, a town over from logging in? They obviously wouldn't be on the same machine, and I want to keep it public for my friends.When you've done that make sure you can connect using a client from inside your network, or on the same machine -
Not anymore. Hamachi gravely destroys my internet connection for some reason. When i did use it, before I learned to Port Forward correctly, people would be disconnected all the time, so did I surprisingly, it would occasionally just crash, my internet would just Die, etc.
That's why I'm here, posting about how its being an issue.
-
This is again where the problem arises, Attached is a .png of my Command Prompt after typing ipconfig, It displays Two IP's, 192.168.0.1, and 192.168.0.2. My Port is currently set to the Former, as it was when I ran a 2.1.1 server, while the server.properties file is set to the latter, again as it was when i ran a 2.1.1 server.
When I set the server.properties file to list 192.168.0.1 It "Fails to bind to Port" though it doesn't display this on 192.168.0.2 . Again Localhost doesn't work but I don't care for that anyway, I connect Via my current IP, given by ipchicken.com, that way I know when its changed and when to Inform my friends of that little factoid. When the Server is running, set on 192.168.0.2, localhost doesn't work, and neither does the IP.
This is why I make the assumption that its something to do with how the Port is Forwarded, or Tekkit just hates me.
-
Thanks for notifying me that LAN IP's don't have to be Censored. Fail on my part. Again I'm new to this forum in particular so All the Rules aren't Nailed into my head yet.
I've attached the Properties File, according to the Attach Button anyway.
As far as I know Its set up correctly, I could attach some Images of my Port Forwarding Page if that's Needed.
-
Please don't Lynch me for this.
I'm not exactly sure where this would go, seeing as I'm not quite sure what the problem is. Let me explain like a good little monkey.
I set up a Tekkit 2.1.1 Server, roughly when it came out, Port forwarded correctly, Server Properties was set correctly, Everything was ready to go. After some Minor Troubleshooting, It was up, it ran just fine with the occasional overload due to a nuclear explosion. Upon Revisiting Technicpack.net one day I stumbled upon the Tekkit Server 3.0.4 Update. Realizing I was completely outdated at the time, due to not playing Tekkit for a while, I downloaded the latest version, and edited the Server Properties accordingly.
Here's the Problem. It doesn't work. The Port forwarding was exactly the same as what was used for Tekkit 2.1.1. Which is why it confused me. The Properties file was edited exactly like the 2.1.1 file, so I wasn't sure why I wasn't able to get anyone to connect.
Now I'm not sure if I'm supposed to, or even if its okay to post Port Forwarding Information, so I'll just say it like this:
My Port is forwarded like this: ###.###.#.1
The Server Properties file had to be like this: ###.###.#.2
And that's just how it worked, I'm not sure why having Two, versus One made it as such. If the Properties file was set to One, or Three then It would display *FAILED TO BIND TO PORT* upon Starting the server.
With Version 3.0.4 however, I am restricted to putting in ###.###.#.2 as my IP to get on, the IP doesn't work, and not even localhost works, which confuses me further.
As a result, I attempted to Re-Portforward it, which I did successfully, and Identically to how it was done before. Yet it still doesn't work.
Could anyone offer insight to what to do to this, or refer me to a page on the Forum I can't find?
And any Mods who tell me where to move this topic to, I shall gladly do that.
Don't Lynch me for this, I'm new to the forum posting system, since I've usually been able to find what I need without being a Registered Member.
Tekkit Server/Port Forwarding Issue/Bug/Glitch/Problem-Whatever
in Tekkit Classic Discussion
Posted
Problem Solved. I think. It Found it. But when I use my current IP:25565 Tekkit doesn't pick it up.