Blockland Forums
Home
Help
Login
Register
Blockland Forums
»
Blockland Forums
»
Help
»
Considering Blockland doesn't 'need' port forwarding anymore, whats usual issues
« previous
next »
Print
Pages: [
1
]
Author
Topic: Considering Blockland doesn't 'need' port forwarding anymore, whats usual issues (Read 663 times)
The Titanium
January 11, 2011, 05:20:23 PM
I've just recently stopped being able to host. I don't think I've changed anything about my connection, but my server now only reads as ---
Few days ago it couldn't even send a brick picture to BL.us or register the fact that it has RTB
It does both I think now, but its ping is always ---
Does anyone know what the general issue normally is?
Ad Bot
Advertisement
Chrono
January 11, 2011, 05:23:59 PM
Could be:
-UPnP is disabled.
-The port is being used.
-Firewall.
The Titanium
January 11, 2011, 05:31:36 PM
Yes, I disabled UPnP but I thought that was for manual port forwarding.
...
Enabling it did nothing at all.
The Titanium
January 11, 2011, 08:26:56 PM
bump
Chrono
January 12, 2011, 01:40:55 AM
UPnP is for automatic port forwarding.
You have to enable it on both Blockland and your router settings, and then restart everything just to be sure.
This includes Blockland, your computer, and your router.
The Titanium
January 14, 2011, 04:52:32 PM
i run norton antivirus, do you know any settings that would block connection?
The Titanium
January 14, 2011, 04:53:11 PM
or anything i could set to allow blockland access?
K3k0m@n
January 14, 2011, 05:47:46 PM
norton gives viruses, not blocks viruses.
The Titanium
January 14, 2011, 06:31:32 PM
no
The Titanium
January 14, 2011, 06:32:46 PM
ive dealt with fallacious 'antivirus' software before
rogue antivirus software
had to get my loving computer fixed because of it
norton is not one of these
Print
Pages: [
1
]
« previous
next »
Blockland Forums
»
Blockland Forums
»
Help
»
Considering Blockland doesn't 'need' port forwarding anymore, whats usual issues