I recently had my router replaced with a higher-end version of the same general model (Actiontec MI424WR). Previously everything was working fine; now when I click "Open to LAN", other computers on the network can't detect it. I can still play over the LAN; it's just that the server isn't automatically detected.
What I'm asking is whether or not there's some setting I may have changed at some point on the old router and forgotten about, that I didn't set on the new router. Has anyone had a similar problem and been able to fix it?
Rollback Post to RevisionRollBack
▀▄▄▀ This creeper isn't happy with his birth defect.
█▀▀█ He made it so you couldn't have more than two lines in a signature.
Probably your computer(s).
Make sure that the network the router is giving out is considered to be a 'home' network by your computers (I assume Windows) and antiviruses.
That's what I thought it might have been as well, but I don't think that's it:
See if it is. Go into Network and Sharing Center.
It should look something like this.
To make it become regarded as a different type of network, click where Home Network is on the screenshot. It should then come up with a dialog like this:
Make sure that's set to Home Network on any machines you're trying to use. Otherwise, I don't know why it would be 'private'.
I'm using Windows 8, and "private" is the new term for "home". It worked before on Windows 8.
Rollback Post to RevisionRollBack
▀▄▄▀ This creeper isn't happy with his birth defect.
█▀▀█ He made it so you couldn't have more than two lines in a signature.
Maybe u have Port-Forwarding for u Minecraft in u old Router?!?
(25565 are normally the Port but i prefer an range from 25550 to 25570 to have the most ports Server Admin use.)
p92 also shows Advanced Filtering a default rule to drop multicast IP on the local ethernet. You might try disabling that.
p95 Security Log may give you additional hints about why the multicast LAN announcements are being received. You might need to enable the packet logging (and then disable it later on to avoid the performance hit)
p92 also shows Advanced Filtering a default rule to drop multicast IP on the local ethernet. You might try disabling that.
p95 Security Log may give you additional hints about why the multicast LAN announcements are being received. You might need to enable the packet logging (and then disable it later on to avoid the performance hit)
The only thing I see relating to IGMP in the Routing section is already checked (just says IGMP under Routing Protocols.) I enabled logging for blocked IGMP Multicast and nothing came up. But I'm not sure what you mean about Advanced Filtering; how exactly would I disable that? I looked in the manual and don't see anything on that page about multicast.
Rollback Post to RevisionRollBack
▀▄▄▀ This creeper isn't happy with his birth defect.
█▀▀█ He made it so you couldn't have more than two lines in a signature.
sorry, I might have accidentally switched from printed page numbers to pdf page numbers.
It's printed page 89, 92nd page of the pdf.
And I certainly didn't mention that rules with destination 224.0.0.0 / 240.0.0.0 are multicast IP address rules.
sorry, I might have accidentally switched from printed page numbers to pdf page numbers.
It's printed page 89, 92nd page of the pdf.
And I certainly didn't mention that rules with destination 224.0.0.0 / 240.0.0.0 are multicast IP address rules.
Nope, no luck. :-( The default setting wasn't there, and adding an explicit "allow" rule didn't work either.
Any other suggestions?
Rollback Post to RevisionRollBack
▀▄▄▀ This creeper isn't happy with his birth defect.
█▀▀█ He made it so you couldn't have more than two lines in a signature.
To post a comment, please login or register a new account.
What I'm asking is whether or not there's some setting I may have changed at some point on the old router and forgotten about, that I didn't set on the new router. Has anyone had a similar problem and been able to fix it?
█▀▀█ He made it so you couldn't have more than two lines in a signature.
That's what I thought it might have been as well, but I don't think that's it:
Notice it says "Private (current profile)"
█▀▀█ He made it so you couldn't have more than two lines in a signature.
I'm using Windows 8, and "private" is the new term for "home". It worked before on Windows 8.
█▀▀█ He made it so you couldn't have more than two lines in a signature.
(25565 are normally the Port but i prefer an range from 25550 to 25570 to have the most ports Server Admin use.)
p92 also shows Advanced Filtering a default rule to drop multicast IP on the local ethernet. You might try disabling that.
p95 Security Log may give you additional hints about why the multicast LAN announcements are being received. You might need to enable the packet logging (and then disable it later on to avoid the performance hit)
The only thing I see relating to IGMP in the Routing section is already checked (just says IGMP under Routing Protocols.) I enabled logging for blocked IGMP Multicast and nothing came up. But I'm not sure what you mean about Advanced Filtering; how exactly would I disable that? I looked in the manual and don't see anything on that page about multicast.
█▀▀█ He made it so you couldn't have more than two lines in a signature.
It's printed page 89, 92nd page of the pdf.
And I certainly didn't mention that rules with destination 224.0.0.0 / 240.0.0.0 are multicast IP address rules.
Nope, no luck. :-( The default setting wasn't there, and adding an explicit "allow" rule didn't work either.
Any other suggestions?
█▀▀█ He made it so you couldn't have more than two lines in a signature.