sa2000 691 Posted yesterday at 04:13 PM Posted yesterday at 04:13 PM @Zenith Media @ebrThe support article has been amended to include Mesh Networks. Troubleshooting Connectivity Issues Checklist
Luke 42184 Posted yesterday at 05:05 PM Posted yesterday at 05:05 PM @Zenith Mediaplease let us know if this helps. Thanks.
Zenith Media 4 Posted 20 hours ago Author Posted 20 hours ago It's an eero Max 7, they refer to it as a modem/router. Along with it, I have a deco mesh system.
ebr 16307 Posted 20 hours ago Posted 20 hours ago 7 minutes ago, Zenith Media said: Along with it, I have a deco mesh system. Why? The Eero is also a mesh system.
Zenith Media 4 Posted 20 hours ago Author Posted 20 hours ago I already had the deco system when I upgraded the internet to ont, it came with eero. We have a lot of devices. It works. I tried the steps. On the deco, I made it an Access Point and enabled Smart DHCP. On the eero interface, I port forwarded the deco with 32700-32700, previously I had 8096-8096. As of now, it does not work remotely, still.
sa2000 691 Posted 18 hours ago Posted 18 hours ago (edited) 1 hour ago, Zenith Media said: On the deco, I made it an Access Point and enabled Smart DHCP. On the eero interface, I port forwarded the deco with 32700-32700, previously I had 8096-8096 the 32700 to 32700 in the support article example was for the case when they were both routers and on the 2nd router you forward 32700 to 8096 You said you made the deco access point - so the network and DHCP is now served by the eero, If you want to use 32700 as the public port, on the eero you forward 32700 to 8096 for the the emby server local IP address - because the deco is now just an extension to the existing eero network Does the eero port forward allow you to have a different public port from the local port i.e. 32700 to 8096 or does it only allow the same port number? if it has to be the same, then you should go back to forwarding 8096 to 8096 on the eero to the local IP of the emby server - assuming you are keeping the deco operating as an Access Point Edited 18 hours ago by sa2000
Zenith Media 4 Posted 1 hour ago Author Posted 1 hour ago Okay, I adjusted the port forwarding through the eero, 8096-32700.
sa2000 691 Posted 1 hour ago Posted 1 hour ago (edited) 18 minutes ago, Zenith Media said: the eero, 8096-32700. So the Emby Server has a local IP address provided by the eero. It is DHCP Reserved or static You have a manual port forward in the eero for Public/WAN/External Port 32700 to forward to Private/LAN/Local tcp port 8096 In Emby Server Settings - Network, you have Public http port number set to 32700 The default Local Http port number is kept as default as 8096 Update: and you have disabled "Enable automatic port mapping" ? correct? Edited 1 hour ago by sa2000
Zenith Media 4 Posted 1 hour ago Author Posted 1 hour ago Reserved. In the eero app, under IP Reservation, Port Forwarding 8096-32700 (Enabled). In Emby Server Network settings, no, the public http port number by default is showing 8096 in the first row and on the second row it is showing the Public https port number 8920. Do I change both of these to 32700? For the local inside of emby Network settings, the first row Local http port number, 8096. The second row Local https port number, 8920
sa2000 691 Posted 45 minutes ago Posted 45 minutes ago (edited) 16 minutes ago, Zenith Media said: 16 minutes ago, Zenith Media said: Port Forwarding 8096-32700 I am concerned this might be a port range 8096 to 32700 Do you have a screen in the eero app like the one below?s If you do, then it needs to be: Name: Emby Port or Port Range: 32700 Use a different port or port range for the internal port: enabled Internal Port or Port Range: 8096 Protocol: TCP ticked and saved Then in Emby Server Network Settings you keep Local http port as 8096 and you set Public Http port as 32700 and you have "Enable automatic port mapping" unticked and Save I am assuming you have "Secure Connections Mode" as "Disabled" If your eero app screen is different, let me have a screenshot Edited 43 minutes ago by sa2000
sa2000 691 Posted 14 minutes ago Posted 14 minutes ago that is good. you don't need to have udp for this - so sufficient for TCP to be ticked Lets check the server network settings - for ports and automatic mapping and secure connections
sa2000 691 Posted 6 minutes ago Posted 6 minutes ago great - only one thing to change: Public http port number - change from 8096 to 32700 and save
sa2000 691 Posted 4 minutes ago Posted 4 minutes ago If you can get me a screenshot of the eero app with tcp only ticked and not with udp, i will use it as an example in the documentation
Zenith Media 4 Posted 2 minutes ago Author Posted 2 minutes ago Okay. So the second Public row, keep it 8920?
sa2000 691 Posted 1 minute ago Posted 1 minute ago 1 minute ago, Zenith Media said: Public row, keep it 8920? That is for https / secure connections and it is disabled - so no need to touch it
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now