Also, try respawning (/spawn or /home), although I highly doubt that'll fix the issue.
When I tried to connect, I didn't get far enough to even try typing.
Are you connecting through locahost (127.0.0.1) or your local IP? Try connecting through your global and see if you can even get on. If global and local aren't working, try bypassing the router and connecting through global.
Rollback Post to RevisionRollBack
If you think the title and OP tells you everything you want to know about a thread, don't reply. If you want to actually read the thread and post an intelligent reply, you're welcome to it.
While looking for an answer for your question, I think I may have discovered the problem. When I try to connect to my own server using my External IP, I get the same problem you and my brother did. I can, however, still connect through my Local IP.
So the problem is with my External IP. I'm still not sure how to fix this, though.
if it were JUST global (external), then I'd point fingers at port forwarding. However, since you're connecting with local and your brother can't, it doesn't seam like port forwarding. Forwarding shouldn't matter on a local network. Have you changed the port in the server properties.txt file at all? If so, what is it?
I'm still curious to know if you can connect without the router in there...
Rollback Post to RevisionRollBack
If you think the title and OP tells you everything you want to know about a thread, don't reply. If you want to actually read the thread and post an intelligent reply, you're welcome to it.
If you think the title and OP tells you everything you want to know about a thread, don't reply. If you want to actually read the thread and post an intelligent reply, you're welcome to it.
If you think the title and OP tells you everything you want to know about a thread, don't reply. If you want to actually read the thread and post an intelligent reply, you're welcome to it.
Yeah, I got the same also. That field should be left blank anyway, except for specific instances. Hmm.. must let smoke from my ears clear for a bit while I percolate on this..
Rollback Post to RevisionRollBack
If you think the title and OP tells you everything you want to know about a thread, don't reply. If you want to actually read the thread and post an intelligent reply, you're welcome to it.
Got home from work and ran this by a roomate. He suggested seeing if your brother is able to host properly. Not sure what it would tell us other than something on your comp is fubar, though. Would be interesting to see what happens.
Rollback Post to RevisionRollBack
If you think the title and OP tells you everything you want to know about a thread, don't reply. If you want to actually read the thread and post an intelligent reply, you're welcome to it.
I had an issue like this once, where people couldn't receive terrain data and then were disconnected...
Turns out avast! was the cause of the trouble turning it off solve the problem
I've done some research myself, and I have found two things likely to be the problem.
1. I am Running Windows XP Service Pack 3
2. I am using an Atheros Network Card
I am now going to try to uninstall SP3, and see if it changes anything; wish me luck.
Haven't upgraded to Win7 yet, yeesh!!! Get with the times!!! :biggrin.gif:
Been using Win7 pro x64 since it was in beta. Love it so much.
Totally forgot about the SP3 issue with hosting. Not used to people flocking to Vista (yuck) or finally upgrading to 7.
Rollback Post to RevisionRollBack
If you think the title and OP tells you everything you want to know about a thread, don't reply. If you want to actually read the thread and post an intelligent reply, you're welcome to it.
Okay, SP3 has been uninstalled, but now instead of getting a "timed out" error, he gets a "connection refused:connect" error. Any idea why this would be happening?
When I tried to connect, I didn't get far enough to even try typing.
Are you connecting through locahost (127.0.0.1) or your local IP? Try connecting through your global and see if you can even get on. If global and local aren't working, try bypassing the router and connecting through global.
So the problem is with my External IP. I'm still not sure how to fix this, though.
I'm still curious to know if you can connect without the router in there...
Didn't change anything.
Turns out avast! was the cause of the trouble turning it off solve the problem
1. I am Running Windows XP Service Pack 3
2. I am using an Atheros Network Card
I am now going to try to uninstall SP3, and see if it changes anything; wish me luck.
Been using Win7 pro x64 since it was in beta. Love it so much.
Totally forgot about the SP3 issue with hosting. Not used to people flocking to Vista (yuck) or finally upgrading to 7.