Thank you Gdkitty
I've tried port forwarding at least 6 times (using solutions each time). When I check online using Portchecker (https://portchecker.co/) the ports are still closed.
Everything I've read online for the Technicolor modems, from anywhere in North America, has no resolution to this issue other than a hardware re-set.
Rogers needs to step up and acknowledge that this is an issue, and of course resolve it either with a Firmware update or swapping of modems to something that allows these ports to open.
@LORDAL, Welcome to the Rogers Community Forums! 😃
As a gamer myself, I know how important it is to be able to do Port Forwarding on your Modem for the best experience when gaming online and streaming.
This is not something that we directly support but if you are unable to do any Port Forwarding then we definitely want to investigate this for you. Please send a Private Message to @CommunityHelps so we can gather your info and get started. Not familiar with our Private Messaging system? No problem, Click Here.
We look forward to hearing from you!
I might have a solution that you can try (I have the same modem)
I set up the local IP network to use a DHCP address range of 10.0.0.100 thru 10.0.0.253.
I added port forwarding for the HTTP service (TCP/UDP) to 10.0.0.253 port 80.
I set up laptop with a server and hardcoded the IPV4 IP to 10.0.0.253, Mask 255.255.255.0, gateway 10.0.0.1 and DNS server addresses as 18.104.22.168 and 22.214.171.124. (Registering DNS and NETBIOS over TCPIP is your optionally your choice).
Lastly, I altered the DHCP range to 10.0.0.100 - 10.0.0.252
http requests are now being routing to my server as expected. (Note that I do not have anything set up for port 443).
Hope this helps...
Thank you for your help.
I took Rogers' advice and performed a hardware reset on my Technicolor 4140. After some anxiety filled moments, the light flashed green, then flashed white. I then connected my laptop to the modem via the Ethernet port and completed the reset procedure.
Ultimately however I believe the problem was that I entered the incorrect Gateway address in my Lorex DVR interface (correct address is 10.0.0.1). Client port 9000 and HTTP port 80 are now open and allowing throughput of camera info.
As a novice, many networking terms are used but not fully explained, cause countless hours of confusion and frustration. Port forwarding procedures have an abundance of these...
If I understand correctly, the XB6 port forwarding does not work. I have such modem. Do you have a date for the fix?
Thanks in advance.
I have been blowing my brains out trying to solve this issue since setting up a new desktop and thought it was something I was doing. This REALLY sucks. I work in IT and allowing a firmware build to go out the door with such an obvious flaw and such an inconvenience to customers is, IMHO, inexcuseable.
My Ignite TV and Internet experience has been a VERY bumpy road and I can honestly say that I am close to the breaking point after 20+ years of being with Rogers. Too many years of releasing hardware, software and features a quarter baked.
I do understand your frustration. I was also at a breaking point.
In my case however, I realized that I had made a fundamental error within my DVR settings.
The reality of this situation has stuck with me, since I needed to rack my own brain and both Lorex and Rogers would not or could not provide help of a networking specialist.