Connection works for a while then gets this : [DBMSLPCN]SQL Server does not exist or acces

Situation:
We have some custom code running on microsoft great plains **under
terminal services** on a windows 2003 machine.
We have a program (running under great plains) that will run for about
5 minutes, then give the error
[Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does not exist
or access denied.
I've tried disabling the shared memory protocol in the client network
utility. That didn't have any effect...even though the error points to
the shared memory protocol.
Now, I've got aql running on a non-standard port or 1150. If I change
this back to the default 1433, the program works fine.
Any ideas why?
Steven Vallarian
Hi
You may look at netstat to see what is connected to the ports of use PortQry
to see if you can connect:
http://support.microsoft.com/default...b;en-us;310099
It may be that you just have general network problems such as a faulty
switch.
John
"svallarian" <svallarian@.hotmail.com> wrote in message
news:1109778822.752029.318690@.l41g2000cwc.googlegr oups.com...
> Situation:
> We have some custom code running on microsoft great plains **under
> terminal services** on a windows 2003 machine.
> We have a program (running under great plains) that will run for about
> 5 minutes, then give the error
> [Microsoft][ODBC SQL Server Driver][DBMSLPNCN]SQL Server does not exist
> or access denied.
> I've tried disabling the shared memory protocol in the client network
> utility. That didn't have any effect...even though the error points to
> the shared memory protocol.
> Now, I've got aql running on a non-standard port or 1150. If I change
> this back to the default 1433, the program works fine.
> Any ideas why?
>
> Steven Vallarian
>