<div>
What are you trying to do with rules. If the purpose is to access the clients computers/laptops then a good way to make it easy for you is to use DHCP reservations on the server. for example you could use the mac adddress for the LAN to have a reserved ip. and let the wifi get the dynamic one. &nbsp;The resrved IP can be used all the times to access. <br />
<br />
Make sure to have the reservation set of IPs different from the DHCP such as 100-199 dhcp and 1-99 reservations. <br />
<br />
Also try to ping both IPs to confirm they were assigned. <br />
<br />
If that doesn't work for you install Wins which as it might help. <br />
<br />
hope this helps
</div>


What are you trying to do with rules. If the purpose is to access the clients computers/laptops then a good way to make it easy for you is to use DHCP reservations on the server. for example you could use the mac adddress for the LAN to have a reserved ip. and let the wifi get the dynamic one.  The resrved IP can be used all the times to access.

Make sure to have the reservation set of IPs different from the DHCP such as 100-199 dhcp and 1-99 reservations.

Also try to ping both IPs to confirm they were assigned.

If that doesn't work for you install Wins which as it might help.

hope this helps

<div>
<div class="content wysiwyg-content">
Our firewall allows for dynamic rules. &nbsp;When a client has two IP's assigned via DHCP, only one shows in DNS with NSLOOKUP. &nbsp;How can I get DNS to show both IP's assigned so that firewall rules will consider BOTH connections/IP's?
</div>
</div>


Our firewall allows for dynamic rules.  When a client has two IP's assigned via DHCP, only one shows in DNS with NSLOOKUP.  How can I get DNS to show both IP's assigned so that firewall rules will consider BOTH connections/IP's?

Windows 2003 nslookup reports only 1 IP for client with LAN &amp; WIFI Connection

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

Windows 2003 nslookup reports only 1 IP for client with LAN &amp; WIFI Connection

Windows 2003 nslookup reports only 1 IP for client with LAN & WIFI Connection