Connect via NIC card instead of DNS record?

[Lewis_Spokane]

We have laptops that use the LAN when connected, then auto-switches to the WLAN when disconnected. Lansweeper knows the LAN address because it is listed with the "Network" value, however, if you ping or otherwise try to connect to a machine through Lansweeper it uses the DNS record instead. When deploying packages is there a way to use the IP address and not the DNS record?

We have an unresolved DNS issue where the WLAN address is the DNS record even if it has been plugged into the LAN for a week. (but that's not a Lansweeper problem)

[Lewis_Spokane]

Well, I figured out our DNS problem so that should fix our issue deploying things via the netBios name anyway. But the option to deploy to an IP could come in handy someday.

Thanks for the info.

[CyberCitizen]

A scheduled task on your scanning server for ipconfig /flushdns?

[Esben_D · Accepted solution]

Unfortunately, the deployment module only uses netbios name to connect and can't use IP address. I'll link your topic to the existing feature request for this.