Re: Applied patches, and network share on copier now inaccessible

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Aug 7, 8:46 pm, Mesan <935m...@xxxxxxxxx> wrote:
On Aug 7, 3:03 pm, Susan Bradley <sbrad...@xxxxxxxxxxx> wrote:





Mesan wrote:
On Aug 7, 1:56 pm, Susan Bradley <sbrad...@xxxxxxxxxxx> wrote:
Mesan wrote:
On Aug 7, 1:02 pm, Susan Bradley <sbrad...@xxxxxxxxxxx> wrote:
Mesan wrote:
Last saturday I applied ISA 2004 SP3, Security Update for SQL 2000 SP4
KB948110, Security update for Exchange 2003 SP2 KB950159, Security
Update for Server 2003 KB951748, Security Update for Server 2003
KB948110, .Net 3.0 SP1 KB929300, Security update for Server 2003
KB951746, Group Policy Client Side Extensions for Server 2003 KB943729
and Malicious software removal tool - July 2008 KB890830.
One on those must have changed something because I can no longer
access the file share on my copier.  My SBS server is 192.168.16.2
(sound familiar?), the copier is 192.168.16.63.  I can ping the
copier's ip address just fine - I can even ping its hostname.  The web-
page for the copier comes up without a problem, so I know that it's on
the network and talking OK.  The problem though comes when I try to
access the network shares on the copier.
If I try to access them directly (net view \\192.168.16.63) I get a
System Error 51.  If I try to use the hostname (net view \\estudio35)
I get a System Error 53.
Everything was working just fine before I installed all those patches
on Saturday, but now no one can access the shares on the copier. :(
Any ideas?
Look in the ISA logs to see if it's blocking anything.
I'd power cycle the copier as well.- Hide quoted text -
- Show quoted text -
I set a monitoring query in ISA for the copier's IP address -
everything looks good, there are no errors saying that things are
blocked.
I disabled SMB signing...no difference (yet).
I rebooted the copier earlier today, but not since disabling SMB
signing - I'll give that a try.
Thanks Susan!  Please don't give up on me! :)
If that doesn't work, take the Windows security patches out and reapply
them one at a time.- Hide quoted text -

- Show quoted text -

No, turning off SMB signing didn't make a difference (even after
turning off the power to the copier).
You're suggesting to
1) remove the windows security updates
2) test and make sure I can access the copier
3) assuming I can access the copier, apply the security updates one by
one, making sure that I can always access the copier.

Is that right?

Yup.

It might be ISA but I don't think so but keep that in mind.

Don't think it's SQL.
Nor Exchange
Nor Group policy
Nor .NET

Duh before you rip these out
I'll betcha there's ports this needs and the DNS patch is stomping on them.

Pull that patch off, do a netstat -ano see what that copier is listning
on and put in a exclusion for those ports.

See this KB for what I'm talking about:

Service issues on SBS-based systems
After you install this security update, and then you restart a computer
that is running Microsoft Windows Small Business Server 2003 (Windows
SBS), you may experience many network-related problems.

For more information about this issue, click the following article
number to view the article in the Microsoft Knowledge Base:
956189 (http://support.microsoft.com/kb/956189/) Some services may not
start or may not work correctly on a computer that is running Windows
SBS after you install the DNS Server security update 953230 (MS08-037)- Hide quoted text -

- Show quoted text -

I uninstalled both the DNS patches and I'm not seeing any different
behavior.  I uninstalled them one at a time, rebooting after each, but
I still get those same errors (system error 51 and system error 53).

:-(  This isn't good - what else could it be???

Mesan- Hide quoted text -

- Show quoted text -

What makes this really frustrating is that pinging the ip address,
pinging the hostname, browsing to the built-in webpages...they all
work. It's just accessing the stinking file shares that doesn't
work. :-( Grrr...

I'm stuck. stuck good.
.

Relevant Pages

  • Re: Applied patches, and network share on copier now inaccessible
    ... I just don't understand how any Windows update on the server could block ... You said that you had a problem when you "try to access the network shares ... Does your copier actually have a hard drive in it that stores ...
    (microsoft.public.windows.server.sbs)
  • Re: Applied patches, and network share on copier now inaccessible
    ... Update for Server 2003 KB951748, ... , the copier is 192.168.16.63. ... take the Windows security patches out and reapply ... After you install this security update, and then you restart a computer that is running Microsoft Windows Small Business Server 2003, you may experience many network-related problems. ...
    (microsoft.public.windows.server.sbs)
  • Re: Applied patches, and network share on copier now inaccessible
    ... Update for Server 2003 KB951748, ... , the copier is 192.168.16.63. ... take the Windows security patches out and reapply ... After you install this security update, and then you restart a computer ...
    (microsoft.public.windows.server.sbs)
  • Re: Applied patches, and network share on copier now inaccessible
    ... Update for Server 2003 KB951748, ... , the copier is 192.168.16.63. ... I get a System Error 53. ... After you install this security update, and then you restart a computer ...
    (microsoft.public.windows.server.sbs)
  • Re: Applied patches, and network share on copier now inaccessible
    ... Update for Server 2003 KB951748, ... , the copier is 192.168.16.63. ... take the Windows security patches out and reapply ... After you install this security update, and then you restart a computer ...
    (microsoft.public.windows.server.sbs)