Ethernet Gateway 4 Not Connecting to iMonnit Online Troubleshooting Guide
Updated: 2 days ago
When an Ethernet Gateway 4 will not connect to iMonnit Online, the cause is usually one of a few things: the gateway is not assigned to the account, it does not have a working network path, DNS cannot resolve the destination, outbound traffic is blocked, or the gateway needs a firmware update.
This guide walks through the checks in a practical order. Start at the top and work down. That gives Monnit Support the clearest picture if the gateway later needs diagnosis or repair.
If a gateway may require repair, best-effort troubleshooting steps directed by Monnit Support must be completed before a Return Material Authorization form, or RMA, is issued.
Start with what the Ethernet Gateway 4 needs to connect
The Ethernet Gateway 4, often called the EGW4, uses a local Ethernet network to reach iMonnit Online. iMonnit Online is also known as the Default Interface.
For the gateway to report data, several conditions must be true:
The gateway must be added to an iMonnit Online account.
The gateway must be powered and complete its startup test.
The gateway must have a valid IP address on the local network.
The Ethernet switch or network port must support a 10/100 Mbps Ethernet connection.
The network must allow traffic to the Internet over outbound TCP port `3000`.
The network DNS server must resolve `sensorsgateway.com`.
The gateway firmware should be current if an update is available.
The key detail is that the gateway sends data out. The required port is outbound TCP port `3000`. An inbound port is not specified for this connection.
Confirm the gateway has been added to iMonnit Online
Before looking at cables, firewalls, or switch settings, confirm that the gateway exists in the correct iMonnit Online account.
A gateway that has not been added to an account may have power and network access, but it will not appear correctly in the portal. The portal needs the device record before it can receive and associate the gateway’s data.
Check the following:
The iMonnit Online account has been created.
The gateway has been added to the correct account.
The gateway has been added to the correct network within the account.
The device ID and security code were entered correctly.
The account is the one expected by the person checking the portal.
If no account exists yet, create the account first. Then add the gateway using the device information provided with the unit. If sensors are already tied to a different network or account, confirm the gateway is being added where those devices are expected to report.
This step sounds simple, but it prevents wasted time. A gateway can look offline in one account while it was added somewhere else.
Check power and the startup test
Once the account setup is confirmed, check the gateway itself. A connection issue can begin before the device ever reaches the network.
Confirm that:
The power supply is connected firmly.
The power outlet is active.
The gateway powers on consistently.
The gateway completes its startup test.
No connector is loose or damaged.
The Ethernet cable clicks securely into the gateway.
If the gateway does not power on or fails during startup, document the behavior before resetting or moving anything. Note the LED pattern, the cable arrangement, and any changes that happened before the failure.
A useful test is to move the power supply to a known working outlet. If another compatible power supply is available and approved for the device, Monnit Support may ask you to test with it. Do not substitute random adapters. Incorrect voltage or current can damage equipment.
Verify the local Ethernet connection
The EGW4 must operate on a local Ethernet network with a valid IP address. If the gateway cannot join the local network, it cannot reach iMonnit Online.
Start with the physical Ethernet path.
Check the cable:
Try a known working Ethernet cable.
Confirm the cable latch is not broken.
Avoid damaged patch cables, couplers, or wall plates during testing.
Connect directly to a known working switch port if possible.
Check the switch port:
Look for link lights on the switch.
Move the gateway to another known working port.
Confirm the port is enabled.
Confirm the port is assigned to the expected network or VLAN.
Avoid ports configured only for devices with special authentication unless the gateway has been approved for that setup.
The Monnit Ethernet Gateways support 10/100 Mbps Ethernet. That matters because some managed switches or special ports may not negotiate correctly with 10/100 Mbps devices. The switch, router, or media converter connected to the gateway must be compatible with 10 or 100 Mbps Ethernet.
If the switch port is forced to a setting the gateway does not support, change the port to auto-negotiate or to a compatible 10/100 Mbps setting. If the gateway is connected through a fiber media converter, industrial switch, or PoE splitter, simplify the path. Test through a basic known working Ethernet switch before moving back to the original connection.
Confirm the gateway has a valid IP address
A gateway must have a usable network address before it can connect to the Internet. In most networks, a DHCP server assigns that address automatically. In more controlled networks, a static address or DHCP reservation may be used.
The practical goal is the same: confirm the gateway is present on the local network and has an IP address that fits that network.
Ask the network administrator to check:
Whether the gateway appears in the DHCP lease table.
Whether the assigned address is in the correct subnet.
Whether the gateway is on the intended VLAN.
Whether the gateway has the correct gateway address for Internet access.
Whether any access control list is blocking the device.
If the gateway does not appear in DHCP, the issue may be physical link, DHCP scope exhaustion, VLAN mismatch, MAC filtering, or switch port configuration. If it does appear but still cannot connect, the issue may be DNS, routing, or firewall rules.
A stable IP address also helps Support. When reporting the issue, include the assigned IP address if available, along with the subnet and gateway address if your policy allows sharing that information.
Test outbound TCP port 3000 access
The EGW4 needs access to the Internet over outbound TCP port `3000`. This is one of the most common causes when a device is powered, connected, and visible on the local network but still does not connect to iMonnit Online.
Many business, school, government, and industrial networks restrict outbound traffic. Web browsing may work from a laptop because ports `80` and `443` are open, while port `3000` remains blocked.
Ask the network administrator to confirm that the gateway can send outbound TCP traffic on port `3000`.
The rule should allow:
Requirement | What to allow |
Direction | Outbound |
Protocol | TCP |
Port | `3000` |
Destination name | `sensorsgateway.com` |
Inbound port | Not specified |
Do not create unnecessary inbound rules. The connection requirement is outbound. Opening inbound ports can create security concerns without helping the gateway connect.
If the network uses a firewall, proxy, or traffic inspection appliance, check whether non-browser traffic is blocked by default. Some systems allow only approved applications or approved destination categories. The gateway needs a direct permitted path for its outbound connection.
Confirm DNS can resolve sensorsgateway.com
The gateway must be able to resolve `sensorsgateway.com`. If DNS fails, the gateway may have a valid IP address and Internet access but still fail to find the correct destination.
This check is especially important on networks with custom DNS filtering, private DNS servers, or restricted Internet access.
From a device on the same network segment, ask the network team to test DNS resolution for:
` sensorsgateway.com `
If DNS does not resolve, check:
The DNS server assigned to the gateway’s network.
Whether the DNS server can resolve public hostnames.
Whether DNS filtering blocks the domain.
Whether the VLAN has different DNS settings than the test computer.
Whether the gateway is using a restricted guest or isolated network.
Testing from a laptop can help, but only if the laptop is connected to the same port type, VLAN, and firewall policy as the gateway. A laptop on Wi-Fi may not prove that the wired gateway network has the same access.
Update the gateway firmware if available
If the account setup, power, local network, DNS, and outbound port are all correct, check whether a firmware update is available for the gateway.
Firmware updates can address device behavior, compatibility, and communication issues. Follow the official instructions for the gateway model and avoid interrupting power during the update process.
Before updating, gather the current device information:
Gateway model
Gateway device ID
Current firmware version if visible
iMonnit Online account or network name
Description of the connection problem
Steps already completed
After the update, allow the gateway time to restart and reconnect. Then check iMonnit Online again. If it still does not connect, record the time of the test. That timestamp can help Support compare device activity against server-side logs.
Use a simple isolation test when the cause is unclear
If the gateway still will not connect, reduce the network to the simplest possible setup. This helps separate a device problem from a network policy problem.
A good isolation test uses:
A known working power outlet.
A known working Ethernet cable.
A simple switch or router that supports 10/100 Mbps Ethernet.
A network known to allow outbound TCP port `3000`.
DNS that can resolve `sensorsgateway.com`.
If the gateway connects on the simple network, the original network is likely blocking or misrouting the connection. Return to switch settings, VLAN settings, firewall rules, DNS, and outbound port policy.
If the gateway does not connect on a known working network, collect the test details and move toward Support review.
This is also a good point to avoid repeated random changes. Changing cables, ports, firewall rules, account settings, and firmware all at once can make the real cause harder to find. Change one thing, test, then document the result.
What to collect before contacting Monnit Support
Clear notes can shorten the support process, especially if an RMA may be needed later. Before contacting Monnit Support, gather as much of the following as you can.
Item | Why it helps |
Gateway device ID | Identifies the exact unit |
Account and network name | Confirms where the gateway should report |
Power behavior | Shows whether startup completes |
LED behavior | Helps identify device state |
IP address if assigned | Confirms local network presence |
Switch model or port type | Helps check 10/100 Mbps compatibility |
Firewall result | Confirms outbound TCP port `3000` status |
DNS result | Confirms `sensorsgateway.com` can resolve |
Firmware version | Shows whether an update is needed |
Time of last connection attempt | Helps compare logs and test results |
Support may ask you to repeat some steps under direction. That is normal. Best-effort troubleshooting must take place before an RMA is issued for diagnosis or repair.
Quick troubleshooting checklist
Use this checklist when working through an Ethernet Gateway 4 connection problem.
Confirm the gateway is in iMonnit Online
Make sure it has been added to the correct account and network.
Check power and startup
Confirm the device powers on and completes its startup test.
Inspect the Ethernet connection
Test with a known working cable and switch port.
Verify 10/100 Mbps compatibility
Confirm the switch or connected device supports the gateway’s Ethernet speed.
Confirm a valid IP address
Check DHCP leases, VLAN assignment, subnet, and gateway address.
Allow outbound TCP port `3000`
Make sure the firewall allows the gateway to send traffic out on TCP port `3000`.
Confirm DNS resolution
Verify that `sensorsgateway.com` resolves from the same network path.
Update firmware if available
Apply available firmware updates using the official process.
Run an isolation test
Try a simpler known working network to separate network policy from device behavior.
10. Document everything for Support
Keep notes on tests, results, times, and network details.
What a successful connection looks like
A successful Ethernet Gateway 4 connection is not just a powered device with an Ethernet cable attached. The gateway should be added to iMonnit Online, complete its startup test, receive a valid local network connection, resolve `sensorsgateway.com`, and send outbound traffic over TCP port `3000`.
If those requirements are met, the gateway should be able to deliver data to iMonnit Online. If it still cannot connect after these checks, the next step is to contact Monnit Support with your notes. That gives Support the information needed to guide further testing and determine whether repair evaluation or an RMA is appropriate.
Need help with your application?
ProSense Instruments — explore instruments, sensors, data loggers and test equipment.
ProSense Solutions — discuss complete monitoring and automation systems.
ProSight Software — explore cloud dashboards, alarms and reporting. Device integration must be confirmed for your application.
Instrument enquiries: sales@prosenseinstruments.com.au | 1800 560 854
Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.
Comments