Front End connectivity to the network is always trouble

  • Thread starter Thread starter Frank Situmorang
  • Start date Start date
F

Frank Situmorang

Hello,

For some users they alwasy have problem for not able to connect to the
backend in the server.

The problem is as follows. In the server we have allowed users to connect to
the Server and the security is without pasword for the user to connect
therefore the options User must changed password at next log on is "
Unticked". But we do not know what makes it later " Ticked" then some users
can not access anymore the server from their Front Ends.

What I do is to delete the user and recreate again user for them and make
the option "unticked", then it works again.

But in one week or 2 weeks ( no regular interval) the same problem happens
again.

My question is what makes it happened and how can we solve this problem.

Thanks very much for any helps.
 
If you are using XP as backend, it is limited to 10 connections for a share:
Right click on the shared folder to have the context menu, select the
"Sharing and Security...' menu item, and near the middle of the dialog
which appears, you should see there is an "Allow this number of users" which
cannot exceed 10, on XP. Have to have a Server OS (or maybe Vista) to
increase this limit.


Vanderghast, Access MVP
 
Does the limit of 10 apply if you're *NOT* using security? And by XP I assume
you're referring to Windows XP as opposed to Access XP (Access 2003).
 
Thanks Michel for your response, may be we need to give more information. The
OS in our server is Windows 2000 professional. Does it have also limit for
the user? and coulcd it be the problem, because as I said as soon as I
recreated again for the same user and untick the option, it works again.
 
I don't have Windows 2000 Pro installed anywhere where I could test it, but
from memory I would say that since it is not an OS Server, it MAY be that
the same limit of 10 users, max, is applicable. Sure, your problem can be
something else too, and have nothing to do with that limit. The easiest way
to test it would be to test it by putting the back-end on a OS-Server (NT
4.0 Server, Windows 2000 Server, etc. ).

Other source of problem could be a wrong connection: if you use cable, be
sure there is no electrical motor close to you cable, anywhere on its
length. Note that a connection problem is likely to occur always with the
same sub-set of machines, while, on the other hand, a user limit would
problem, in theory, would occur on any machine, more or less randomly
(unless the 11th user is always the same guy who always arrive late at the
job, so is always the one coming after the '10' other user made their
connection without problem). A connection problem, with cable, can also
occur if the screws holding the various threads of the cable, in the wall,
got loose, or if there is more than 5 hubs total on the local network, or if
you use more than 3 hubs with connections to machines (other than other
hubs), or a cable length in excess of its recommended length, etc. Sure,
'software' guys have a tendency to blame the 'hardware', so maybe the
hardware is not the source of the problem at all.


It is hard for me to say go for a Server OS (if you have none at the moment,
to test it), since the problem can be elsewhere and, if so, that would be an
expense (not only buying the OS, but also installing it, testing it, etc..)
that will not solve the problem, and that would not make you happy, in the
end.



Vanderghast, Access MVP
 
So if we're running on Windows Server 2003, there shouldn't be any issues
with more than 10 users accessing the backend?
 
Sure, if the limit is waved out (as raising the maximum number of users to
99, as example, for that share directory / file ).


Vanderghast, Access MVP
 
Thanks Michel for your response, may be we need to give more information. The
OS in our server is Windows 2000 professional. Does it have also limit for
the user? and coulcd it be the problem, because as I said as soon as I
recreated again for the same user and untick the option, it works again.
Click to expand...


I just checked ... yes, W2K also has the 10 user limit.

RD
 
I am not sure RD, if 10 users limit is the problem, because I noticed they
are more than 10 users accessed that server at one time, but there is no
problem occurrs. I am just confused what to do now. Yes..the company will
alwasy need me in order to keep the system working, but I am not happy with
my work because I am the one who created the " Supplier Invoice Tracking
database". If I am not here anylonger I do not want to loose my reputation
because of this problem.

Thanks if anyone can still have any idea
 
I am not sure RD, if 10 users limit is the problem, because I noticed they
are more than 10 users accessed that server at one time, but there is no
problem occurrs. I am just confused what to do now. Yes..the company will
alwasy need me in order to keep the system working, but I am not happy with
my work because I am the one who created the " Supplier Invoice Tracking
database". If I am not here anylonger I do not want to loose my reputation
because of this problem.

Thanks if anyone can still have any idea
Click to expand...

Frankly, I think this is an issue with your server, not your
application. I went back and read your other posts and, after much
ruminating and cogitating, I figure there must be some other factor at
work. Perhaps another process (or person) is messing with the user's
permissions?

If neither of those are the issue then I'm at a loss.

Good luck,
RD
 
Back
Top