|
|
There are no limitations imposed by BITS on IP address configuration. You
were probably getting the error under DHCP configuration because of DNS
problems. Check if you could resolve the fully qualified name of the server
by pinging it from the client machine.
By the way, you don't need to resume a job entering into a transient error.
BITS will automatically do this for you guided by the parameter
MinimumRetryDelay
(http://msdn.microsoft.com/library/en-us/bits/bits/ibackgroundcopyjob_setminimumretrydelay.asp).
The default retry delay is 10 minutes. You can reduce it if you want BITS to
retry often using the API pointed to by the above link.
--
Narayana Mahankali
Microsoft, BITS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
www.microsoft.com/info/cpyright.htm">http://www.microsoft.com/info/cpyright.htm
"Edward" <code.samurai@xxxxxxxxx> wrote in message
news:1115353083.788828.288320@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I used BitsAdmin.exe to diagnose the problem and under DHCP
> configuration I was getting:
> ERROR CODE: 0x80072ee7 - The server name or address could not be
> resolved
> ERROR CONTEXT: 0x00000005 - The error occurred while the remote file
> was being processed.
>
> When the machine's configuration was changed to static BITS could
> proceed with the downloads. I would like to know if there are any
> limitations to the client machine's configuration where BITS would not
> work.
>
> Thanks,
> Edward
>
|
|