> I went to port forwarding/port triggering [...]
On what, exactly? (Firmware version?)
> [...] typed in the port (25565) selected TCP/UDP and my internal IP
> address (192.168.1.10) [...]
In-line pictures in these forums are delayed until a moderator
approves, so I can't (yet) see what you did, and, in any case,
copy+paste of plain text is usually more useful than a picture of plain
text.
Have you done anything (like address reservation) to ensure that this
(unspecified) server always has the same LAN IP address?
> [...] just like I've done in the past.
With my weak psychic powers, that non-description conveys no actual
information.
> And I also have an Arris modem [...]
Not a very detailed description of anything. Model?
> [...] so I port forwarded on that too [...]
Not even a non-picture in that non-description. Again, copy+paste of
the actual port-forwarding rules would have been helpful. However, if
you're doing port forwarding there, then it sounds like a modem+router,
not simply a modem. Cascading multiple routers can cause multiple
problems, probably including this one.
If your (unspecified) Netgear router (of some sort) is intended to
provide better wireless coverage, then you may want to configure it as a
wireless access point instead of as a full-function router, and leave
all the router functions (like port forwarding) to your (unspecified)
Arris modem(+router).
Alternatively, if you're not using the router functions of your
(unspecified) Arris modem(+router), then you may want to configure it as
a modem-only, and leave all the router functions (like port forwarding)
to your (unspecified) Netgear router (of some sort).
> [...] I've read a bunch of forum posts [...]
Can't guess what those might have been, either.
> [...] have been trying for about 4 hours now [...]
Can't see what you were doing, either.
