--- title: "Connecting to the Network" canonical: "https://docs.infoblox.com/space/BloxOneInfrastructure/204801131/Connecting%20to%20the%20Network" format: markdown --- To activate a server connection to the Infoblox Portal by using the Device UI: > ⚠️ After installing the image, if a physical appliance is rebooted without the network cable, the appliance does not automatically obtain a DHCP lease address when the cable is later connected using GE1. To configure the appliance in this situation, access the Device UI by following steps 2 and 3. 1. Connect the network cable to the GE1 port on the back panel of the appliance. The other ports do not work until after the appliance has used GE1 to connect to the Infoblox Portal. Once the appliance is connected to the Infoblox Portal using GE1, the other interfaces on the appliance can be configured. 2. If the network does not have a DHCP server, or if the appliance cannot obtain a DHCP lease, the appliance uses the default IP address 192.168.1.2/24. To access the physical appliance, connect the workstation to the same network and assign it an IP address in the same subnet, such as 192.168.1.3/24. 3. Open the internet browser on the workstation. If the IP address was not allocated via the DHCP server in your network, then enter **[https://192.168.1.2](https://192.168.1.2)**.** ** - If the IP address was allocated via the DHCP server in your network, then enter **https://********. 4. Enter the following credentials for local access: - **Username**: Enter **admin** as the login username of the NIOS-X server. - **Password**: Enter the seven-digit serial number of the appliance. Obtain the serial number from the Service Tag label on the bottom of your appliance. 5. The Device UI appears in the browser. Select the **Network Mode** according to whether you are using the DHCP or a static IP, and then enter information for the IP address. 6. If required, update the DNS Resolver and NTP server settings. > 📝 - Infoblox uses Universal DDI DNS (`52.119.40.100`) as the default DNS resolver. This IP must be whitelisted in your firewall or ACL for successful connectivity. If the health check fails or the IP is not reachable, we recommend using a custom DNS resolver as a fallback to ensure uninterrupted DNS resolution. The health check information is available on the Device UI or serial console. > 📝 - Infoblox uses `ntp.ubuntu.com`, `time.google.com`, or `time.windows.com` as the default NTP servers. If the health check fails, we recommend using a custom NTP server to maintain accurate time synchronization. The health check information is available on the local UI or serial console. 7. To submit the changes, click **Apply Changes** on the Device UI. > 📝 When connecting a hardware appliance to the Infoblox Portal, ensure that you DO NOT enter the join token in the Device UI. Otherwise, the appliance will lose connectivity to the Infoblox Portal when the server certificate expires. Instead, use the serial number of the NIOS-X physical server to connect to the Infoblox Portal. > 📝 When changing the IP address configuration of a port on a physical appliance, make sure that the port is plugged into the network and UP. If it is not, the changes may not apply. After you have set up the appliance successfully, you will not be able to access the Device UI again unless connection issues occur with the appliance, in which case you can use the Device UI to perform some troubleshooting tasks for the appliance. For more information, see *[Troubleshooting Hosts](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/184681229)*. If you need to re-configure the appliance, you must first reset it to the factory default. In addition, if you have not configured any NTP server or local DNS resolver, the appliance will use the Ubuntu NTP server (`ntp.ubuntu.com`, `time.google.com`, or `time.windows.com`) and Universal DDI DNS (IP: 52.119.40.100). Because these services do not communicate via an HTTPS proxy, you must ensure that the NTP port (UDP 123) and the DNS port (TCP/UDP 53) are open on your firewall. ## Troubleshooting Network Connection If the NIOS-X server does not connect to the Infoblox Portal, check the following: - Verify that the network setting is correct. For more information, see *[Troubleshooting Hosts](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/184681229)*. - Ensure that the serial number on the appliance matches the serial number of the NIOS-X physical server you created in the Infoblox Portal. For more information, see *[Viewing Host Status](https://infoblox-docs.atlassian.net/wiki/pages/createpage.action?spaceKey=BloxOneInfrastructure&title=Viewing%20Host%20Information)*.