1 of 1 people found this helpful
repeater needs to resolve the targets. how else can it initiate a connection ?
I get that, but how does file deploy job with repeater work?
We have same server acting as a proxy and repeater
Sounds pretty strange, I can browse the server, file deploy job can resolve the name , works always, but deploy job don't...
you sure the file deploy job is using the repeater ?
do you see the deploy payload coming from the repeater in that case ?
I know it sound strange, payload is getting transferred via repeater, coz firstly thread is copying it to repeater and after that it invoke transfer to the targets.
Without repeater transfer was taking around 2-3 hours, but now its working in 30-40 mins for 3 servers.
The flie deploy works differently than the normal deploy – though I’d expect it to need to resolve the targets too so I’m not sure why it works.
Well we finally resolved this issue by opening some firewall connections from DNS Server to proxy server and after that Repeater is working fine with both file deploy and blpackages.
But unfortunately , we ended up in an opposite issue when we tried same thing for another network.
In this case Blpackage works fine with repeaters but file deploy gives an error for all servers.
kdkkaod01.bddian.local is my repeater server.
Error 1.12.2014 12:48:31 (kdkkaod01.bddian.local) The system cannot find the file specified.
can you post the full job run log from that ?
what file can't be found ?
Sorry couldn't reply back with logs due to security issues.
I found out the exact issue though, environment variable for rscd agent were not updated till we restart the agent of repeater, this lead to issue while invoking nsh from the repeater to transfer file.
Thanks for help..