Can't connect to Windows Server 2003 drives

Hi,

We have a Windows Server 2003 File Server which has a database and a custom Application on it.
About 40 - 50 users will either run the application on the server or remote desktop to a different terminal server and run the application from there.
For years this has worked without too many problems then 6 months ago our users which remote desktop were saying that they could not run the application anymore. When I remoted in to the Terminal Server it showed that the mapped drives on the file server were disconnected.
I can remote into the File Server and the drives look ok.
If I go to Network and click on the server it says "Windows cannot access \\server".
Then our local network users were saying that sometimes they could run it but it was slow or sometimes they couldn't run the app at all.
It will sometimes show an "Access Violation" error and not allow the app to run.
I can still run small local MS Access apps which can connect to the database on the server and retrieve data but can't run apps which are installed on the File Server.
So our network tech says that there is an issue with licenses on the file server which is causing this. We have 75 licenses and only about
40 - 50 users. He said that Windows wasn't "letting go of some users" and he reapplied the licenses which has fixed this issue for about 6 months.
Now the problem has come back and our Network tech said that we were only able to reapply the licenses once and now will have to move the whole app to another machine. This doesn't sound entirely right ...
Has anyone heard of this issue before?
Any suggestions as to what is going on?

Thanks,
Stuart
LVL 1
DiscoStubaccaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lionel MMSmall Business IT ConsultantCommented:
Since support for server 2003 ends in July I would call Microsoft and tell them what is going on. I know there are some suggestions on how to "force" terminal server to free up licenses but this may be a method your network tech already used. https://support.microsoft.com/en-us/kb/957553 but you may simply want to check if it is a licensing problem to start with by going to start>programs>admin tools> terminal service licensing and see if all the licenses are indeed been used up/assigned.
0
arnoldCommented:
The error deals with the access to the share
not the drives locally.
One thing to check on the fileserver is that there are no stale sessions to the TS which prevent its access. (computer management interface, shares section.
i.e. \\server is not accessible, is \\IP_of_server?
can you ping the server from your TS or anywhere else.  Check the IPS of the TS and the Fileserver.

Were any firewall work/network done about six months ago i.e. something like DMzing the TS server? Placing restriction on which IP segments can access the fileserver?

...

if it started six months ago, either an MS update causing the issue or network changes were made impacting.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pgm554Commented:
Is this a SBS server?
0
DiscoStubaccaAuthor Commented:
Thanks for all the responses.
It's not SBS server, it is Windows Server 2003 Standard SP2.
We are moving away from Server 2003, we just need to keep it going for another 6 months or so.
Whatever the network tech has done with licensing has settled down the local machines and for the remote users I have mapped the drives using the IP address instead of Share name which works.
The only downside is that we get a security warning every time something is run but you can just ignore that and continue so it's good enough for six months.
I still don't understand how licensing can cause network instability, I thought it would either just shut users out or allow them in not have these fairly random effects.
Thanks,
Stuart
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.