dcom app over slow wan link

[paulpsmith]

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 &quot;dcom time out&quot;. Too many to list for &quot;dcom&quot;<br>
<br>
Thanks<br>
<br>
Paul

 

[MikeLacey]

Paul,<br>
<br>
I have posted your query in the DCOM forum. The folks there might very well be able to help you.<br>
<br>
Mike<br>
<p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>

 

[calahans]

Hi Paul,<br>
<br>
Can I just check if your app interacts with a database over the WAN? <br>
<br>
C

 

[paulpsmith]

Yes there is a database running on the NT WS over the WAN. This is the master phonebook file. There is also a smaller version of the file with a different name that runs locally. The app is a paging system, where the server does all the work and the clients attach to it via tcp/ip. Most clients use the main database, but it has grown in size to over 10meg. It takes the client about 3-4 minutes to open over T1, but it would take about 15 minutes to open over 256 or below. This is because it has to load all the entries in the master phone book. There is a personal phone book that can be kept on the users PC. This just has a couple of users needed at the site. This opens quickly.<br>
<br>
Thanks

 

[paulpsmith]

I forgot to add that using the local phone book only opens over 128+ WAN link. I get an error when I try over 56k link. I don't remember what the exact wording was, but when I did a search at MS Tech Net I got a bunch of VB hits from the index query.<br>
<br>
Thanks<br>
<br>
Paul

 

[calahans]

We had a situation where an app was performing very fast over a network, but was extremely slow over a WAN. We resolved it to the fact that we used a server side cursor, fine over the network but, slow over a WAN.<br>
<br>
With a server side cursor, obviously, the records are retreived one by one as the app needs them. This generates a lot of network traffic.<br>
<br>
We changed our cursor location to client (increasing memory overhead on client) and the app ran fine.<br>
<br>
Maybe you have a similar problem.<br>
<br>
C

 

[paulpsmith]

You have gone beyond what I know about. I am just a lowly LAN admin, with not too many years under my belt. <br>
<br>
Is this server side cursor something the vendor can work on, or is it something I need to do to the server?<br>
<br>
Any Tech Net articles on this?<br>
<br>
Thanks <br>
<br>
Paul

 

[calahans]

You need to talk to your vendor about this. In LAN terms, a client side cursor will make one call to the database and the database will return all records in one go, however a server side cursor will make one call per record and the db will return one row per time = heavy LAN traffic!<br>
<br>
Your vendor may be able to implement the changes, if the application is not to big. Its only a matter of changing an option on connection to the database.<br>
<br>
Let me know if I'm not clear enough.<br>
<br>
C

 

[paulpsmith]

Thanks, I will try to see if they know anything.<br>
<br>
Paul