More autoconnect rules?

Portal User asked a question.

March 2, 2018 at 8:00 AM

Here is another question regarding autoconnect rules, specifically IP address. I have started going through the list of devices that do not fall into an Organization because of incorrect PC name, etc. That is our main autoconnect rule, device naming, so I have started adding the IP to the autoconnect rules for specific sites to pick up those stragglers that are not named correctly.

My question is related to the IP address the client is showing. For example I added this IP as an autoconnect rule for a specific site, 10.1.101.%. A lot have multiple IP's (must be because of multiple network adapters), show they show up like this in the reports, 0.0.0.0,0.0.0.0,0.0.0.0,169.254.157.205,0.0.0.0,10.1.100.187. This is one I want to show up in that site based on 10.1.101.%, but it appears it may only look at the first IP and move on? In this case the real IP is 5th in the string.

Any way around this? Or do I have another issue as to why this is not working?

BTW: Autoconnect rule with this IP address works for other machines with single IP for this wildcard.

thank you.

Oliver Berger (Flexera Software)
8 years ago
Hi Mark, yes, that's how it currently works. The workaround is to use also a '%' at the beginning. It is just tsql searching a string. Of course, due to the limitations of the mask, you could not separate between i.e.192.%.%.% and 182.% .%.% if you can only enter %82.%.%%. and %10.%.%.% could also be 210 or 110. As usual: Feature Requests welcome. Hope that helps. Best Oliver
Expand Post
- blackjack
  7 years ago
  And for the lazy, here is the link to the thread I found:
  Expand Post