CAN'T CONNECT TO SERVER

[leosky]

I setup a ftb server with the latest Direwolf20 pack (1.1.1), downloaded the new server but my friend gets "Cannot connect to server"
I portforwarded correctly and made 2 inbound rules in the advanced firewall options (TCP &UDP).
What could be the problem?
I have a static ip (in the past it was dynamic but I changed it because they told me it would help with this problem).
I can connect via localhost, at least there's that...

 

[rhn]

I setup a ftb server with the latest Direwolf20 pack (1.1.1), downloaded the new server but my friend gets "Cannot connect to server"
I portforwarded correctly and made 2 inbound rules in the advanced firewall options (TCP &UDP).
What could be the problem?
I have a static ip (in the past it was dynamic but I changed it because they told me it would help with this problem).
I can connect via localhost, at least there's that...

Don't double post....

So you set the server up on the same PC that you connect to from the client? If so then have you dealt with the normal Windows firewall settings?

 

[leosky]

Don't double post....

So you set the server up on the same PC that you connect to from the client? If so then have you dealt with the normal Windows firewall settings?

The firewall is turned off completely

 

[leosky]

I realized that was a 100+ post thread so there was no point posting. but it was too late

 

[leosky]

I've had this problem for more than a year. Posted several times on here and NOBODY could help me. Nobody.

 

[TheHawkeye]

Most people on here know more about mods than servers, would recommend trying to use Google or look up a tutorial to making a server correctly.

 

[leosky]

Most people on here know more about mods than servers, would recommend trying to use Google or look up a tutorial to making a server correctly.

Everytime I tried I followed the most viewed/most recent tutorials on youtube to the word. Didnt work. Tried to search on google for my specific problem and got only port forwarding/adv firewall rules

 

[Hambeau]

If your server is at your home then the Static IP address has to come from your ISP, if they offer such.

First, a few definitions:
LAN - Local Area Network. This is the plug you use to connect your computer to your router
WAN - Wide Area Network. This is the plug on your router that connects to your ISP. Can be integrated in the router or a separate modem.
NAT - Network Address Translation
Public Address - An IP address that is valid on the greater internet, I.E. a leased and assigned address and not a Private Address.
Private Address - Any address that falls within 3 ranges:
Class A = 10.0.0.1 - 10.255.255.255
Class B = 172.16.0.1 - 172.31.255.255
Class C = 192.168.0.1 - 192.168.255.255
These addresses are free for anyone to use but can only exist on the LAN side of a router... They are automatically filtered and dropped if encountered on the WAN side, both incoming and outgoing.

If your server has a Private address then no external client will ever connect without additional configuration of one or both routers. WAN addresses are assigned by your ISP. Some ISPs actually assign Private addresses which is a bit more problematical but not insurmountable.

For example, Comcast assigned a Public address to the WAN side of my Cable Modem/Router, while my internal, or LAN address is Private.

Using NAT, my router wraps my Private Addressed packets into a new packet with my WAN address as the originator. This way my packets can transverse the internet. When they return the router dis-assembles the packets and restores them to their original address.

There are ways around this...

1). Plug your friend's computer in at your house (probably not feasible)
2). Set up a "Proxy" address on your router.
3). Set up a VPN (Virtual Private Network) between your router and your friend's router
4). Use a 3rd party server program... The one I've seen mentioned in these forums is something like "Hibachi", except that's a small barbeque

TL;DR: If you want to start messing around with networks be prepared to learn a lot of stuff

 

[leosky]

If your server is at your home then the Static IP address has to come from your ISP, if they offer such.

First, a few definitions:
LAN - Local Area Network. This is the plug you use to connect your computer to your router
WAN - Wide Area Network. This is the plug on your router that connects to your ISP. Can be integrated in the router or a separate modem.
NAT - Network Address Translation
Public Address - An IP address that is valid on the greater internet, I.E. a leased and assigned address and not a Private Address.
Private Address - Any address that falls within 3 ranges:
Class A = 10.0.0.1 - 10.255.255.255
Class B = 172.16.0.1 - 172.31.255.255
Class C = 192.168.0.1 - 192.168.255.255
These addresses are free for anyone to use but can only exist on the LAN side of a router... They are automatically filtered and dropped if encountered on the WAN side, both incoming and outgoing.

If your server has a Private address then no external client will ever connect without additional configuration of one or both routers. WAN addresses are assigned by your ISP. Some ISPs actually assign Private addresses which is a bit more problematical but not insurmountable.

For example, Comcast assigned a Public address to the WAN side of my Cable Modem/Router, while my internal, or LAN address is Private.

Using NAT, my router wraps my Private Addressed packets into a new packet with my WAN address as the originator. This way my packets can transverse the internet. When they return the router dis-assembles the packets and restores them to their original address.

There are ways around this...

1). Plug your friend's computer in at your house (probably not feasible)
2). Set up a "Proxy" address on your router.
3). Set up a VPN (Virtual Private Network) between your router and your friend's router
4). Use a 3rd party server program... The one I've seen mentioned in these forums is something like "Hibachi", except that's a small barbeque

TL;DR: If you want to start messing around with networks be prepared to learn a lot of stuff

My ISP gave me a dynamic IP address, or at least it was like that since I remember, and I set it to static because someone told me it would help for the server (my internal is 10.0.0.10)
I cant believe that there's not a simple solution to this problem... What does my computer have that it makes it not be able to run a server? I shouldn't have to pass a Network+ in order to play Minecraft!
I'm sure I've overlooked something simple, it's always like this.
I tried checking on canyouseeme.org with the server running but it told me "Error: I could not see your service on 2.233.21.104 on port (25565) Reason: Connection timed out"

 

[leosky]

If your server has a Private address then no external client will ever connect without additional configuration of one or both routers. WAN addresses are assigned by your ISP. Some ISPs actually assign Private addresses which is a bit more problematical but not insurmountable.

The "serverip" line has a blank, so it should pick up my public IP automatically. How do I check if I was assigned a private address?
But now that I think about it I was once able to run a server, maybe it was with hamachi, but still