3-party remote control and %AGENTIPADDR% bug?
Updated: 22 May 2010 | 2 comments
This issue has been solved. See solution.
I have manually added a solution to remote control clients. In the remotecontroltools.ini file I use %AGENTIPADDR% as a parameter so I can connect to the client. The problem is that %AGENTIPADDR% sometimes returns the IP 0.0.0.0.
If I take a look at the network adapters in DS I can see 2.
1) A wireless adapter that is not connected with ip 0.0.0.0.
2) A lan adapter that is connected and has a valid ip.
Is this a bug or does %AGENTIPADDR% just return the IP of the first network adapter regardless if the client is connected to the DS thru it or not?
The Aclient interface on the client shows the valid ip.
DS 6.9 build 164.
discussion Filed Under:
Comments
Myself and others at our university are having the same problem. Has anyone found a solution or work around for this?
- Jason
Hi.
I installed SP1 and it seems to resolve the problem.
Same computer.
Nic 1) wlan with IP 0.0.0.0
Nic 2) lan with valid IP.
Echo AgentIPadr: %AGENTIPADDR%
Returns the ip from nic 2.
Would you like to reply?
Login or Register to post your comment.