Aclient binding

[Ed Cox]

Got a customer with a question I can't answer:

Target servers are BL20Ps - Win2K. The first nic is connected to the "RDP" lan and the second nic is connected to the Production lan. The Aclient is binding itself to the second nic which is on a different network than the RDP server sits on. I can't seem to find a way to tell Aclient to use the first nic and not the second. We've tried reordering the bindings, looking under the aclient.inp for a clue, etc.
Anyone have any ideas?
Thanks!
Ed

[Jeff Allen_5]

the aclient seems to bind itself to the first NIC it finds. To get around this, it is indeed in the bindings. Move the RDP NIC to the top of the binding order and stop and start the aclient service.

[Ed Cox]

That's what I had asked the customer and he said he already tried this...but I'm not so sure he did. I'll have him do this while I watch...and then we'll restart the aclient.
thanks Jeff,
Ed

[Ed Cox]

FYI...
Looks like the reordering of the bindings didn't do the trick. SO...
We changed the metric for the "unwanted" nic to a metric of 100 and left the desired nic at 1. Then we found a file called customdata.ini and changed the reference MAC address to that of the desired nic and then restarted the Aclient. That solved the problem.