> This page is for Firmware, version 4.0 (default).
> For other versions, use one of these documentation indexes:
> - 4.0 (default): https://docs.ouster.com/sensor-docs/firmware/4.0/llms.txt
> - 3.2: https://docs.ouster.com/sensor-docs/firmware/3.2/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ouster.com/sensor-docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ouster.com/sensor-docs/_mcp/server.

# Windows

> Host network setup for connecting to an Ouster sensor on Windows.

Tested on Windows 10. The sensor hostname is `os-991234567890.local` (serial number on the sticker on top of the sensor).

## Connecting the Sensor

1. Connect the sensor to an available Ethernet port on the host machine or router.
2. The sensor automatically obtains an IP address via link-local or DHCP, depending on network configuration.

> **Note**
>
> It can take up to 60 seconds to obtain an IP address after initial power-up.

## The Sensor Homepage

1. Enter `http://os-991234567890.local/` in your browser's address bar to open the sensor homepage.

> **Note**
>
> If the sensor homepage does not load, follow the steps in [Determining the IPv4 Address of the Sensor](#determining-the-ipv4-address-of-the-sensor) to verify the sensor has a valid IP address.

## Determining the IPv4 Address of the Sensor

1. Open a Command Prompt by pressing **Win+X**, then **A**.

2. Ping the sensor to find its IPv4 address:

**Command**

```shell
ping -4 [sensor_hostname]
```

**Example**

```shell
C:\WINDOWS\system32> ping -4 os-991234567890.local
```

> **Note**
>
> If this command hangs, configure your interface to link-local first.

**Response**

```text
Pinging os-991234567890.local [192.0.2.130] with 32 bytes of data:
Reply from 192.0.2.130: bytes=32 time<1ms TTL=64
Reply from 192.0.2.130: bytes=32 time<1ms TTL=64
Reply from 192.0.2.130: bytes=32 time<1ms TTL=64
Reply from 192.0.2.130: bytes=32 time<1ms TTL=64

Ping statistics for 192.0.2.130:
  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 0ms, Maximum = 0ms, Average = 0ms
```

> **Note**
>
> In this example, the sensor IPv4 address is `192.0.2.130`. An address of the form `169.254.x.x` means it is connected via link-local.

3. Alternatively, resolve the sensor IP using `dns-sd`:

**Command**

```shell
dns-sd -G v4 [sensor_hostname]
```

**Example**

```shell
C:\WINDOWS\system32> dns-sd -G v4 os-991234567890.local
```

**Response**

```text
Timestamp     A/R  Flags   if   Hostname                     Address        TTL
14:22:46.897  Add  2       6    os-991234567890.local.  192.0.2.130    120
```

> **Note**
>
> An address of the form `169.254.x.x` means the sensor is connected via link-local.

## Determining the IPv4 Address of the Interface

1. Open a Command Prompt by pressing **Win+X**, then **A**.

2. View the IPv4 address of your interfaces:

**Command**

```shell
netsh interface ip show config
```

**Example**

```shell
C:\WINDOWS\system32> netsh interface ip show config
```

**Response**

```text
Configuration for interface "Local Area Connection"
    DHCP enabled:                         Yes
    IP Address:                           169.254.1.100
    Subnet Prefix:                        169.254.0.0/16 (mask 255.255.0.0)
    InterfaceMetric:                      25
    DNS servers configured through DHCP:  None
    Register with which suffix:           Primary only
    WINS servers configured through DHCP: None

Configuration for interface "Loopback Pseudo-Interface 1"
    DHCP enabled:                         No
    IP Address:                           127.0.0.1
    Subnet Prefix:                        127.0.0.0/8 (mask 255.0.0.0)
    InterfaceMetric:                      75
    Statically Configured DNS Servers:    None
    Register with which suffix:           Primary only
    Statically Configured WINS Servers:   None
```

* In this example, the sensor is plugged into interface `"Local Area Connection"`.
* The host IPv4 address is on the `IP Address:` line — here, `169.254.1.100`.

> **Note**
>
> An interface address of the form `169.254.x.x` means Windows self-assigned a link-local address in the absence of a DHCP server.

## Setting the Host Interface to DHCP

Set the interface to obtain an IP address automatically via DHCP. Useful for plug-and-play setups.

**Command**

```shell
netsh interface ip set address ["Network Interface Name"] dhcp
```

**Example** — with interface name `"Local Area Connection"`:

```shell
C:\WINDOWS\system32> netsh interface ip set address "Local Area Connection" dhcp
```

**Response:** (no output)

## Setting the Host Interface to Static IP

Assign a static IPv4 address to the interface. Useful when the sensor must send data to a specific IP.

**Command**

```shell
netsh interface ip set address name="Network Interface Name" static [IP address] [Subnet Mask] [Gateway]
```

**Example** — with interface name `"Local Area Connection"` and IPv4 address `192.0.2.1/24`:

```shell
C:\WINDOWS\system32> netsh interface ip set address name="Local Area Connection" static 192.0.2.1/24
```

> **Note**
>
> `/24` is shorthand for Subnet Mask `255.255.255.0`.

**Response:** (no output)

## Finding a Sensor with mDNS Service Discovery

The sensor announces itself on the network via mDNS with service type `_ouster-lidar._tcp`. Use [Bonjour Browser](https://hobbyistsoftware.com/bonjourbrowser/) to locate all sensors on Windows.

**Example using Bonjour Browser:**

Step 1: Download [Bonjour Browser](https://hobbyistsoftware.com/bonjourbrowser/).

![Downloading Bonjour Browser](/sensor-docs/_fern-files/_img/7b3317d62141684c21a3d8f6656bdec6e683730dabf87622df668291a20456de.webp)

![Bonjour Browser setup and installation](/sensor-docs/_fern-files/ouster.docs.buildwithfern.com/66d0de04b346dac840bc1a3c8c1d70b0e657f4d0c15590bd8c4e5a7f0286e381/assets/common_images/networking/setup_bonjour.png)

Step 2: The sensor appears under `_ouster-lidar._tcp`. Click it to view all sensor details.