How do you do it through Norton? I got that stupid 60 day trial and my firewalls are controlled by that.
It might be that, not 100% sure.
Destroy, remove and obliterate all traces of Norton. I despise that program.
Most likely you're software firewall (windows/norton) is causing the block in this case. I don't use either as I rely on hardware for my home systems so I can't help much there other than disabling them through the control panel.
I used blank, and then I used my internal 192.168.1.104 ip. Neither worked. left it at the intenal for the following questioins.
I had them forwarded previously, and I forwarded them again. Do you have to port forward modems and routers? I only did the router because that's what worked before.
I used my internal 192 to connect by LAN. It worked. Then I tried to connect using the WAN(external) ip. It didn't work.
i get "connection refused: connect"
This is dumb
If you can't connect on your local network. Something is wrong internally.
Are you running the server on the same system you're connecting? If yes, can you connect to 127.0.0.1?
As I can only see one picture, showing your internal IP, there is not enough information to tell me anything.
How do you know the port is, "closing" each day?
What is your network topology? Do you have a router? Are all your friends connecting through internal network ID's (all 192.168.1.x)? There is no where near enoguh information to even venture a guess at the solution.
Map based off of the 2nd Cullen Prime 393050634124102232869567034555427371542904833.
Map 0 has been incredibly fun and interesting. Decent mountains in several spots, good mix of water and clay. The underground has been the most interesting part.
Several abandoned mines found so far, the majority cut by a large ravine. A large amount of natural linking cave structure, spent about 12 hours real life exploring one set and still never found the end. I found the lava light at the end of the tunnel though.
One abandoned mine had at current count 5 spider spawners in close proximity. I think there was more but I started to get overwhelmed. Another cave strucuter had 2 spawners, skeletons, withing 20 blocks of each other in seperate rooms.
It's been a great map so far. Resources not underloaded, but not overloaded either.
I recently ran into this problem this weekend on my home network.
Originally I was running the server off of my local machine and had no issues other than the lack of ram and lag caused by running it. In an attempt to fix that issue I migrated everything over to my main server.
Quad Core Pentium setup with HT, and 18gigs of ram. Very shortly after the migration, with three people on the server I started to get this error. Next I locked the server down and connected with only 1 person, same issue, so it wasn't client related (I always check as some people use client side mods).
After some digging on the internet I found the buffer fix that Notch had posted to the net. However, this only increased the time between dropped clients, 30 minutes versus 10.
Next, I ran into some more information that said it was specifically related to certain gigabit network cards.
Sunday morning I changed my gigabit card full duplex to 100mbit full duplex. The problem has not repeated since.
1) Right click My computer
2) Properties
3) Hardware Tab
4) Device manager
5) Expand network adapters
6) Right click your card, properties
7) Advanced Tab
8) Flow Control
9) Set to 100mbps/Full duplex (or 10 if you're already at 100)
10) Apply settings
11) Test server
My guess is something in the server code just doesn't quite play well with the network layer running at gigabit speeds with certain chipsets or drivers, but this is only a guess and assumption. My server hasn't had this issue as of doing this fix though.
Unfortunately, this is somewhat of a hack fix. It will affect your internal network system to system transfer speeds, unless you're lucky and running two gigabit nics like I am.
I recently ran into this problem this weekend on my home network.
Originally I was running the server off of my local machine and had no issues other than the lack of ram and lag caused by running it. In an attempt to fix that issue I migrated everything over to my main server.
Quad Core Pentium setup with HT, and 18gigs of ram. Very shortly after the migration, with three people on the server I started to get this error. Next I locked the server down and connected with only 1 person, same issue, so it wasn't client related (I always check as some people use client side mods).
After some digging on the internet I found the buffer fix that Notch had posted to the net. However, this only increased the time between dropped clients, 30 minutes versus 10.
Next, I ran into some more information that said it was specifically related to certain gigabit network cards.
Sunday morning I changed my gigabit card full duplex to 100mbit full duplex. The problem has not repeated since.
1) Right click My computer
2) Properties
3) Hardware Tab
4) Device manager
5) Expand network adapters
6) Right click your card, properties
7) Advanced Tab
8) Flow Control
9) Set to 100mbps/Full duplex (or 10 if you're already at 100)
10) Apply settings
11) Test server
My guess is something in the server code just doesn't quite play well with the network layer running at gigabit speeds with certain chipsets or drivers, but this is only a guess and assumption. My server hasn't had this issue as of doing this fix though.
Unfortunately, this is somewhat of a hack fix. It will affect your internal network system to system transfer speeds, unless you're lucky and running two gigabit nics like I am.
I recently ran into this problem this weekend on my home network.
Originally I was running the server off of my local machine and had no issues other than the lack of ram and lag caused by running it. In an attempt to fix that issue I migrated everything over to my main server.
Quad Core Pentium setup with HT, and 18gigs of ram. Very shortly after the migration, with three people on the server I started to get this error. Next I locked the server down and connected with only 1 person, same issue, so it wasn't client related (I always check as some people use client side mods).
After some digging on the internet I found the buffer fix that Notch had posted to the net. However, this only increased the time between dropped clients, 30 minutes versus 10.
Next, I ran into some more information that said it was specifically related to certain gigabit network cards.
Sunday morning I changed my gigabit card full duplex to 100mbit full duplex. The problem has not repeated since.
1) Right click My computer
2) Properties
3) Hardware Tab
4) Device manager
5) Expand network adapters
6) Right click your card, properties
7) Advanced Tab
8) Flow Control
9) Set to 100mbps/Full duplex (or 10 if you're already at 100)
10) Apply settings
11) Test server
My guess is something in the server code just doesn't quite play well with the network layer running at gigabit speeds with certain chipsets or drivers, but this is only a guess and assumption. My server hasn't had this issue as of doing this fix though.
Unfortunately, this is somewhat of a hack fix. It will affect your internal network system to system transfer speeds, unless you're lucky and running two gigabit nics like I am.
0
I was going to ask next if your modem had an internal router in it. Many do these days.
0
This may be a dumb question:
Did you give them your external IP and not your internal IP?
0
Destroy, remove and obliterate all traces of Norton. I despise that program.
Most likely you're software firewall (windows/norton) is causing the block in this case. I don't use either as I rely on hardware for my home systems so I can't help much there other than disabling them through the control panel.
0
If you can't connect on your local network. Something is wrong internally.
Are you running the server on the same system you're connecting? If yes, can you connect to 127.0.0.1?
0
Are you running a gigabit network anywhere?
0
Better is subjective. Higher resolutions have more detail per block face, take more memory, and require to you put some unofficial support into place.
0
Windows firewall enabled?
0
How do you know the port is, "closing" each day?
What is your network topology? Do you have a router? Are all your friends connecting through internal network ID's (all 192.168.1.x)? There is no where near enoguh information to even venture a guess at the solution.
0
Map 0 has been incredibly fun and interesting. Decent mountains in several spots, good mix of water and clay. The underground has been the most interesting part.
Several abandoned mines found so far, the majority cut by a large ravine. A large amount of natural linking cave structure, spent about 12 hours real life exploring one set and still never found the end. I found the lava light at the end of the tunnel though.
One abandoned mine had at current count 5 spider spawners in close proximity. I think there was more but I started to get overwhelmed. Another cave strucuter had 2 spawners, skeletons, withing 20 blocks of each other in seperate rooms.
It's been a great map so far. Resources not underloaded, but not overloaded either.
0
0
I was runnin vanilla as well when I had the issue start.
Just an edit too, this needs to be done to the server, not the client side.
0
Thanks.
This particular issue gave me no end of headaches as it just seemed to come out of nowhere this weekend and no one seemed to have a reliable fix.
Hopefully this will fix your problem as the symptoms sound virutally identical to what I had.
*edit*
Do this to the server, not the client. Though, I'm not 100% this won't help the client yet. I did not need to change this on my client at home.
1
Originally I was running the server off of my local machine and had no issues other than the lack of ram and lag caused by running it. In an attempt to fix that issue I migrated everything over to my main server.
Quad Core Pentium setup with HT, and 18gigs of ram. Very shortly after the migration, with three people on the server I started to get this error. Next I locked the server down and connected with only 1 person, same issue, so it wasn't client related (I always check as some people use client side mods).
After some digging on the internet I found the buffer fix that Notch had posted to the net. However, this only increased the time between dropped clients, 30 minutes versus 10.
Next, I ran into some more information that said it was specifically related to certain gigabit network cards.
Sunday morning I changed my gigabit card full duplex to 100mbit full duplex. The problem has not repeated since.
1) Right click My computer
2) Properties
3) Hardware Tab
4) Device manager
5) Expand network adapters
6) Right click your card, properties
7) Advanced Tab
8) Flow Control
9) Set to 100mbps/Full duplex (or 10 if you're already at 100)
10) Apply settings
11) Test server
My guess is something in the server code just doesn't quite play well with the network layer running at gigabit speeds with certain chipsets or drivers, but this is only a guess and assumption. My server hasn't had this issue as of doing this fix though.
Unfortunately, this is somewhat of a hack fix. It will affect your internal network system to system transfer speeds, unless you're lucky and running two gigabit nics like I am.
*edit*
Do this to the server, not the client.
0
Originally I was running the server off of my local machine and had no issues other than the lack of ram and lag caused by running it. In an attempt to fix that issue I migrated everything over to my main server.
Quad Core Pentium setup with HT, and 18gigs of ram. Very shortly after the migration, with three people on the server I started to get this error. Next I locked the server down and connected with only 1 person, same issue, so it wasn't client related (I always check as some people use client side mods).
After some digging on the internet I found the buffer fix that Notch had posted to the net. However, this only increased the time between dropped clients, 30 minutes versus 10.
Next, I ran into some more information that said it was specifically related to certain gigabit network cards.
Sunday morning I changed my gigabit card full duplex to 100mbit full duplex. The problem has not repeated since.
1) Right click My computer
2) Properties
3) Hardware Tab
4) Device manager
5) Expand network adapters
6) Right click your card, properties
7) Advanced Tab
8) Flow Control
9) Set to 100mbps/Full duplex (or 10 if you're already at 100)
10) Apply settings
11) Test server
My guess is something in the server code just doesn't quite play well with the network layer running at gigabit speeds with certain chipsets or drivers, but this is only a guess and assumption. My server hasn't had this issue as of doing this fix though.
Unfortunately, this is somewhat of a hack fix. It will affect your internal network system to system transfer speeds, unless you're lucky and running two gigabit nics like I am.
*edit*
Do this to the server, not the client.
0
Originally I was running the server off of my local machine and had no issues other than the lack of ram and lag caused by running it. In an attempt to fix that issue I migrated everything over to my main server.
Quad Core Pentium setup with HT, and 18gigs of ram. Very shortly after the migration, with three people on the server I started to get this error. Next I locked the server down and connected with only 1 person, same issue, so it wasn't client related (I always check as some people use client side mods).
After some digging on the internet I found the buffer fix that Notch had posted to the net. However, this only increased the time between dropped clients, 30 minutes versus 10.
Next, I ran into some more information that said it was specifically related to certain gigabit network cards.
Sunday morning I changed my gigabit card full duplex to 100mbit full duplex. The problem has not repeated since.
1) Right click My computer
2) Properties
3) Hardware Tab
4) Device manager
5) Expand network adapters
6) Right click your card, properties
7) Advanced Tab
8) Flow Control
9) Set to 100mbps/Full duplex (or 10 if you're already at 100)
10) Apply settings
11) Test server
My guess is something in the server code just doesn't quite play well with the network layer running at gigabit speeds with certain chipsets or drivers, but this is only a guess and assumption. My server hasn't had this issue as of doing this fix though.
Unfortunately, this is somewhat of a hack fix. It will affect your internal network system to system transfer speeds, unless you're lucky and running two gigabit nics like I am.
*edit*
Do this to the server, not the client.