Re: XP Pro client crashes after logging in to SBS2003 domain
- From: "Immedia" <Immedia@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 19 May 2005 10:06:06 -0700
Thanks everyone, for your responses and ideas. As it turns out, our error was
in deploying all the organizations printers (about 6) to all users via their
login scripts. 2 of the printer drivers were wrong - this caused users to
crash sporadically when they tried to print.
"Jim Behning SBS MVP" wrote:
> I second getting cables certified. It is not hard to do cable the
> right way but many do not. I wish I could have a good teter in my
> toolkit but they cost as much as good server hardware. At least you
> can eliminate the cabling.
>
> I suffered a day and half of workstation troubleshooting. Workstations
> worked fine for accessing email and file transfers. The LOB which is
> sql based with a web interface was slow. I did many thngs including a
> format of a workstation and fresh install of the os and it still slow
> workstations. Changed nics, changed switches, used different patch
> cable. I ended up updating the computer bios and the problems went
> away. These were brand new computers but the bios was dated March a
> year and the November bios fixed the problem. When I tried to use
> their old switch again I had connectivity problems. I suspect marginal
> cables which should be tested. I will suggest that the cables are
> tested once the practice gets to enjoy their new server and computers
> for a few days.
>
> "hb" <model_heli@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >Only a thought but have you considered having the cabling tested
> >independantly with a digital fluke, most certified installers will give you
> >a report of each cable after the test.
> >
> >I have had this done on a few networks I took over and it was amazing how
> >many incorrect outlets came up on the test as being wired incorrectly, main
> >issue we were getting was slowness, lockups and other problems that could
> >not be explained
> >
> >regards
> >
> >H
> >
> >"Immedia" <Immedia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >news:76426810-6760-426D-88C0-1C1861147546@xxxxxxxxxxxxxxxx
> >> I have 35 users on a SBS2003 domain. All XP clients (about 30) log in with
> >no
> >> problems but sporadically crash or have applications freeze with no
> >> discernible patterns. Relevant facts as far as I can tell are
> >> 1. Server itself has never crashed. It is running on fairly robust
> >hardware
> >> - IBM xSeries server, dual Xeon, 2x36 U320 Boot drives, 5 x36GB U320 data,
> >> Dual Gbit Nics. 2GB RAM
> >> 2. The 5 Windows 2000 clients have NEVER had a problem.
> >> 3. We have 45 CALs, it is rare for more than 30 users to be on the network
> >> simultaneously
> >> 4. Crashes SEEM to happen more when there are more users
> >> 5. Crashes SEEM to happen more with printing and Outlook, but other Office
> >> applications are also impacted frequently. There are 4 HP Network printers
> >> being spooled.
> >> 6. The AVERAGE user locks up 3-4 times per day. Some days, some users will
> >> have no problems, on others, the same user will lock up 15-20 times.
> >> 7. There is one other Windows 2000 server in the network serving Great
> >> Plains and another proprietary database.
> >> 8. All XP clients are SP2 using Software Updates from the server.
> >>
> >> Microsoft's own SBS support has not been able to diagnose thus far. We've
> >> checked licensing issues, network architecture, updates, virus software
> >and
> >> many other issues. Rapidly running out of ideas - has anyone seen this
> >happen
> >> before? Saw a similar thread earlier from 11/9/2004 but there did not seem
> >to
> >> be any resolution there.
> >>
> >> Would greatly appreciate any advice! Thanks in advance,
> >>
> >
>
> Jim B. SBS MVP
>
.
- Prev by Date: Site access
- Next by Date: Re: Using Terminal Server in SBS2003 Environment - architecture qu
- Previous by thread: Site access
- Next by thread: Install ISA2004 on SBS2003 Premium questions
- Index(es):
Relevant Pages
|
