Forum
Topic: «RPC errors», Problem with deployment.
« Previous topic | Next topic »
|
Chris Foward
User profile Posts: 1 Joined: 08/18/2008 |
Hello,
I have recently installed DeviceLock at the company where I work. we were getting lots of RPC errors when we initially rolled out the product. We have since discovered that the problem has been caused by a combination of software running together. The software that is running together is TMobiles Web n Walk software and Microsft ISA server. The question that I have is, Has anyone come across this in the past, and if so, is there an easy fix for this? Thank you in advance. |
| Posted: 08/18/2008 13:33:58 | |
|
Ekaterina Vavilova
Technical Support Engineer Editor User profile Posts: 569 Joined: 06/27/2007 |
Did you try to contact Microsoft on this issue?
Probably, there's an upgrade to solve RPC issue. |
| Posted: 08/18/2008 17:56:25 | |
|
davidm
Editor User profile Posts: 77 Joined: 06/30/2006 |
Which RPC error numbers? RPC errors are sometimes very generic and can be caused by a handful of items discussed in the FAQ (firewall/router filtering, RPC service not running, sharing turned off, server service removed/off, etc). The commands may also timeout due to bad DNS Names Resolution performance and come back with RPC errors when all else looks fine... To test this, assign a static address config to an endpoint rather than one from DHCP... then test... If it works right away, Names Resolution is slow...
To test regular connectivity, use your Computer Management program in Administration Tools from the DL console host to connect to the same remote endpoint(s) and attempt something an admin would have access to do...If you see the same problems, it is a network performance issue or endpoint IP config issue generally. |
| Posted: 08/29/2008 02:48:53 |
Stay in contact with us through:
