Re: Windows server 2003 performance problem in Access
- From: "Paul Shapiro" <paul@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 Dec 2005 14:45:01 -0500
I found that Access development was too slow to be feasible until I disabled
the SMB signing as suggested in those articles. Since then the performance
is fine. SMB signing protects your workstations/server from a hostile
computer on the internal network by authenticating all communication with
the server. I think that as long as you're comfortable that there aren't any
hostile computers on the internal network you haven't lost meaningful
security.
Paul Shapiro
"Lance" <lance.schaeffer@xxxxxxxxx> wrote in message
news:1134581734.209753.161440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hello,
>
> I am having some performance problems with an access database. The
> client computers are all running Windows XP SP2, and the server is
> running Windows server 2003. My situation is very similar to the one in
> this old topic at this link.
>
> http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_frm/thread/7188759b0c85bf5a/e9f11abbad2c36b8?lnk=st&q=access+load+time+slow+server+2003&rnum=1#e9f11abbad2c36b8
>
> I tried to respond, but I could not figure out how - perhaps it is old
> and I cannot reply anymore.
>
> My question in response to the fix they suggest, which is disabling the
> security signature requirement, is the security implications this has.
> What exactly does this parameter control, and if i disable it, what are
> the potential affects?
.
- References:
- Prev by Date: Re: Problem connecting 1st time XP Pro client to SBS 2003 server
- Next by Date: Re: SBS 2003 (no SP) - file saving over network suddenly very slow
- Previous by thread: Re: Windows server 2003 performance problem in Access
- Next by thread: Re: Network Slowdown at 5.00 pm
- Index(es):
Relevant Pages
|
