paulpsmith (MIS) Jan 14, 2000 - paul posted this in the VB forum - thought you guys might be able to help.<br>
<br>
Mike<br>
<br>
Have a paging app that runs fine as long as the link is over 128k. Have about five locations using 56k. Get error message when try to run the app over 56k. Vendor thinks it's a time out issue, but has no idea if can increase timeout for dcom. There is a client portion and a server portion. Server portion is running on NT 4.0 WS SP4. Clients are Win95 with restricted policies in place. Is there a reg hack I can use? Is it possable to increase dcom timeout parameter? Checking Technet, no entries under "dcom time out". Too many to list for "dcom"<br>
<br>
Thanks<br>
<br>
Paul <br>
<br>
<p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href= Cargill's Corporate Web Site</a><br>
<br>
Mike<br>
<br>
Have a paging app that runs fine as long as the link is over 128k. Have about five locations using 56k. Get error message when try to run the app over 56k. Vendor thinks it's a time out issue, but has no idea if can increase timeout for dcom. There is a client portion and a server portion. Server portion is running on NT 4.0 WS SP4. Clients are Win95 with restricted policies in place. Is there a reg hack I can use? Is it possable to increase dcom timeout parameter? Checking Technet, no entries under "dcom time out". Too many to list for "dcom"<br>
<br>
Thanks<br>
<br>
Paul <br>
<br>
<p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href= Cargill's Corporate Web Site</a><br>