server issues

[ZombieGunter]

i cant seem to connect to my server i downloaded from the technic website, i type in my ip address with the server on and it says 'cant connect to server' can anyone help? much appreciated!

[Kalbintion]

Are you using "127.0.0.1" or "localhost" for the ip? if not, give it a whirl

[ZombieGunter]

i used localhost but it just gave me a server that doesnt allow the mods i will try the 127 thing

[ZombieGunter]

yeah it didnt work gives me the same server with non working mods :/

[Loader]

Are you using the server download from here?; http://mirror.technicpack.net/Technic/servers/bteam/BTeam_Server_v1.0.9c.zip

 

If you are, you'll need to post on the tracker with more info and logs so we can see what you mean about non-working mods.

Edit: Links for that are in my sig below.

Edited April 2, 2014 by Loader

[ZombieGunter]

i mean by non working mods as if it was like a normal minecraft server, like the items are in the creative tabs, but when i go to place a block down it just disappears and doesnt work, also im typing in my ip and it just says 'can't reach server' dunno what to do :/

 

and yes i was using the server download from there

Edited April 2, 2014 by ZombieGunter

[Kalbintion]

Are you running the "launch.bat" (or "launch.sh" file on non-windows) to start the server? If not, use that file to start the server, otherwise it'll act as a normal minecraft server.

[Loader]

Typing in your WAN (internet) IP will have that effect - what's happening there is you're trying to contact yourself through the internet, without going out to the internet (routers can be dicks, but in this case it's entirely intentional and useful behaviour that keeps LAN traffic safely in the LAN).  127.0.0.1 or localhost are loopbacks which connect to your own computer without even reaching a network adapter (in theory), the 192.168.*.* networks and 10.0.0.* networks are commonly used for internal communication on LANs, and that's what you need to use if you have to use one, not your internet IP.

 

Think of it like trying to ring yourself on the phone you're using to call yourself (it's not a perfect analogy, but if the previous explanation doesn't make sense to you then that's close enough).  Both 127.0.0.1 and localhost are exhibiting normal behaviour for that kind of connection (so those addresses are fine) but the server isn't set up or running correctly, try what Kalbintion suggests.

[ZombieGunter]

so which ip would i put in?

[Loader]

localhost or 127.0.0.1, they're both the same place and both working (it's just a location to connect to and it's doing that - the problem isn't with that).

 

Like Kalbintion asked though, how are you actually running the server?  Which file are you using?

[ZombieGunter]

fixed it!! turns out u were right, i saw a different forum that kalbintion posted somewhere where u do [windows button] + [R] then 'cmd' then u type ipconfig /all then my ip was somewhere in there under pv4 or something!

[Kalbintion]

Odd that using your internal IP address for the network would fix this issue considering 127.0.0.1 (aka "localhost") points to your own machine as well.