Binks7
Technical User
- Aug 1, 2001
- 40
Gentlemen:
I have linked two Win2K PDCs together in order to share an accounting package utilizing the Pervasive 2000 database engine. I have mapped drives to each server. The drive mapping on the clients of the one PDC connected to the PDC running the application disconnects after a short period of time. I have used the net config server /autodisconnect:-1 setting and made sure the registry was changed and rebooted both PDCs. This took care of mapped drives to the host PDC but not the "other" PDC. Question: Is there any other autodisconnect feature or redirector type timeout I am missing? The application (Timberline) ends up aborting after a period of time, and the little red x appears on the drive mapping. A quick click reconnects but Timberline aborts and corrupts data. The Pervasive application uses netbios names to identify hosts. I have mapped the drives both with the IP and netbios name with same result. I appreciate any guidance anyone can give. Thanks
I have linked two Win2K PDCs together in order to share an accounting package utilizing the Pervasive 2000 database engine. I have mapped drives to each server. The drive mapping on the clients of the one PDC connected to the PDC running the application disconnects after a short period of time. I have used the net config server /autodisconnect:-1 setting and made sure the registry was changed and rebooted both PDCs. This took care of mapped drives to the host PDC but not the "other" PDC. Question: Is there any other autodisconnect feature or redirector type timeout I am missing? The application (Timberline) ends up aborting after a period of time, and the little red x appears on the drive mapping. A quick click reconnects but Timberline aborts and corrupts data. The Pervasive application uses netbios names to identify hosts. I have mapped the drives both with the IP and netbios name with same result. I appreciate any guidance anyone can give. Thanks
