Camera Network Addressing in New Caney, TX 77357

Five settings every IP camera has to get right

Camera network addressing is the invisible part of a surveillance install: choosing the IP address each camera, recorder and switch will use, and making sure those choices survive outages, router swaps and the next device someone adds.

Each IP camera carries five pieces of network identity:

• IP address — its unique location on the local network, such as 192.168.20.31.
• Subnet mask — which other addresses it treats as local. A camera set to 255.255.255.0 and a recorder set to 255.255.0.0 can end up able to talk in only one direction.
• Default gateway — the router it uses to reach anything off the local segment. Leave it blank on purpose and the camera cannot phone home to a cloud server; set it wrong by accident and email alerts and time sync quietly fail.
• DNS server — turns names into addresses; alert emails depend on it.
• Time source (NTP) — sits on the same settings page and decides whether your footage timestamps are right.

On top of those sit service ports: web configuration on 80 or 443, RTSP video on 554, and vendor-specific ports such as 8000 on Hikvision gear or 37777 on Dahua gear.

Why a box of identical new cameras fights itself

Many manufacturers ship every unit with the same fixed factory address. Hikvision cameras commonly arrive at 192.168.1.64, and Dahua-built cameras, including several store brands, at 192.168.1.108. Plug four new cameras into a switch at once and you have four devices claiming one address. It looks like a wiring fault: the camera’s web page loads, stalls, then shows a different camera’s settings.

The cure is procedural. We bring cameras up one at a time, or use the maker’s discovery utility — SADP for Hikvision, ConfigTool for Dahua, IP Utility for Axis. Those tools find devices by MAC address rather than IP, so each unit can be activated, given a strong password and moved to its planned address before the next one is connected.

A second collision is easy to miss. A factory address such as 192.168.1.64 can land inside the DHCP pool of a home router that also uses the 192.168.1.x range. The camera works on day one; weeks later the router hands .64 to a phone or smart TV, and both devices start dropping off. The camera did nothing wrong. Nobody moved it out of the router’s pool.

Three ways to hand a camera its address, compared

For most New Caney homes we use the recorder’s plug-and-play network for cameras wired directly to it, and static addresses on a clearly separated range for anything connected through an extra switch. The recorder then has exactly one address on your home network, and that is the only one your phone app needs to know.

The day your internet provider replaces the router

This is the most common reason we re-address a system that used to work. Households in 77357 are on a real mix of service: cable in some subdivisions, fiber in some newer sections, fixed wireless and satellite on wooded acreage off the county roads. Each provider’s gateway picks its own default range — 192.168.1.x on one, 192.168.0.x on another, 10.0.0.x on a third.

When the new gateway goes in, anything set to a static address from the old range is stranded. Cameras on the recorder’s PoE ports keep recording, but a statically set recorder shows offline in the phone app, and the whole system looks dead. Nothing is broken; the recorder lives on a street that no longer exists.

We design around it two ways. The recorder gets a reservation or a documented static address, with a one-page note explaining exactly how to move it if the router is ever swapped. And wherever possible the cameras sit on a range that has nothing to do with the internet provider, so a modem change only ever touches one device.

Remote viewing when your public address is shared

Remote viewing has addressing rules of its own, and rural internet changes them. Many fixed-wireless, cellular and satellite plans — Starlink’s standard residential service among them — put customers behind carrier-grade NAT. The outside address on your router comes from the shared 100.64.0.0/10 range, nobody on the internet can reach your recorder directly, and a port forward simply does nothing.

That is no loss: forwarding ports 80, 554 or 8000 to a recorder is how camera systems end up on public device search engines. What works behind carrier-grade NAT is what we recommend everywhere:

• The manufacturer’s relay (peer-to-peer) service, with a strong unique password, current firmware and only the recorder registered to it — not every camera.
• A VPN into your own router or a small VPN appliance, so the recorder is only reachable once your phone is effectively inside your own network.
• On double-NAT setups, where the provider’s gateway sits in front of your own Wi-Fi router, one of the two goes into bridge or passthrough mode so there is a single, predictable edge.

Individual cameras should normally have no route to the internet at all. We leave their gateway pointed at the recorder or blank, and make the recorder the only device that talks outward.

An address plan that fits the property type

New Caney properties vary widely, and the plan follows the property.

Newer master-planned sections

Homes in the newer communities along the I-69 and Grand Parkway growth corridor usually have a builder media panel and six to ten cameras. The plan is short: cameras on the recorder’s PoE network, the recorder and a Wi-Fi doorbell each reserved on the home router, all of it written down.

Wooded acreage and older lots

On larger wooded lots around Roman Forest, Woodbranch and the county roads, a system often spans the house, a detached shop and a gate, with a second switch in the shop. Those cameras outgrow the recorder’s built-in ports, so we set aside a dedicated range — for example .101 through .140 for cameras, the switch at .2 and the recorder at .10 — and shrink the router’s DHCP pool so it never reaches that block. If pine canopy forces a wireless bridge to the shop, both bridge radios get addresses in the plan too.

Shops, churches and small offices

Card terminals, phone systems and office PCs share these networks, so the cameras go on a separate segment where video never competes with a payment.

Whatever the pattern, every device lands in one table: location, model, MAC address, IP address, recorder channel and firmware version. That sheet is what lets anyone, including us, fix the system later in minutes rather than hours.

What EVOTECH does on a camera addressing call

1. Inventory. A network scan and the maker’s discovery tool list every device actually present, which we compare with the recorder’s channel list. The mismatches are usually the whole story.
2. Clear conflicts. Duplicate and factory-default addresses are moved one device at a time so nothing drops mid-change.
3. Pick the method per device — recorder-assigned, static or reserved — based on how each one connects.
4. Set gateway, DNS and time. Cameras take their time from the recorder; the recorder syncs to a reliable time server and pushes Central time, with daylight saving, to every channel.
5. Harden. Unique passwords, default accounts off, and UPnP disabled so nothing opens ports by itself.
6. Configure remote access that suits your internet service, then test it from a phone on cellular data rather than from inside the house.
7. Power-cycle test. Router and recorder go off and back on together, and we confirm each camera returns to the same address and the same channel.
8. Hand over the address sheet, printed and digital.

EVOTECH serves New Caney from our Katy and Houston base; we do not have a local office in Montgomery County. Before booking, call so we can confirm a date for your address.

What moves the price of an addressing job

• How many cameras there are, and whether they are one brand or a mix of brands with different tools and different default addresses.
• Whether passwords to the existing recorder and cameras are known. A lost admin password can mean a factory reset per device, which wipes each camera’s settings.
• Extra switches, wireless bridges or outbuildings that add network segments.
• Firmware age: an old recorder may need updating before it will accept modern cameras or secure remote access.

You get an itemized quote after we see the equipment.

Addressing shortcuts that bring a technician back

• Leaving a camera on DHCP with no reservation, so after an outage it drifts to a new address while the recorder goes on polling the stale one.
• Typing a gateway that does not exist: the camera records normally, but its clock drifts for months because it never reaches a time server.
• Adding a second router “for more ports,” which starts running its own DHCP and hands out conflicting addresses.
• Forwarding ports for remote viewing instead of using a relay service or a VPN.
• Writing none of it down.

Related services

Frequently asked questions