RE: Printer cannot send SMB to 2003 network

From: william (anonymous_at_discussions.microsoft.com)
Date: 08/12/04 

Date: Thu, 12 Aug 2004 08:32:19 -0700

This was tricky, but it got fixed. For those interested:

The SMB request was sent to the PDC, which caused the copy
machine to lock up. I ran ethereal to watch the
transaction and found that the request was fine, but the
response was to a 169.x.x.x address. Running an SMB
request on another server would respond with the correct
address 192.x.x.x.

Turns out, that the secondary nic on the server was used
during initial install, and was then unplugged. It
assigned itself the exact same 169.x.x.x address that was
being sent to the copy machine. How could an unused NIC
send a response via the used and functional NIC? Well, the
WINS cache had somehow grabbed the 169.x.x.x address and
was using it to respond to the browse request. By
utilizing the secondary WINS server, the problem went
away.

Oh what fun this was to diagnose! Hope this helps someone
that may experience the same problem.

William

>-----Original Message-----
>Hi William,
>
>I can only help you to make sure that the SMB signing is
disabled on the
>Windows 2003 server. In addition, I have included some
settings that I
>thought they might be related to this issue.
>
>1. First review 811497 and disable the policy "Microsoft
network server:
>Digitally sign communications (always)" on the domain.
>
>http://support.microsoft.com/?id=811497
>
>2. Verify Everyone is in the "Pre-Windows 2000 Compatible
Access" group.
>See 325363 and 289655.
>
>http://support.microsoft.com/?id=325363
>http://support.microsoft.com/?id=289655
>
>3. Verify RestrictAnonymous setting. This is configured
by the "Additional
>restrictions for anonymous connections" policy setting.
See 246261, 823659
>for more info.
>
>http://support.microsoft.com/?id=246261
>http://support.microsoft.com/?id=823659
>
>4. After making any policy changes, refresh the policies
settings as
>following command-
>
>gpupdate /force
>
>Thank you again for using our Newsgroup.
>
>Regards,
>Bob Qin
>Product Support Services
>Microsoft Corporation
>
>Get Secure! - www.microsoft.com/security
>
>====================================================
>When responding to posts, please "Reply to Group" via
your newsreader so
>that others may learn and benefit from your issue.
>====================================================
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>

Relevant Pages

  • SMB Signing question, SBS2k
    ... Is the SMB signing issue with XP PRO sp1 and SBS2k still an issue? ... several users complained that copying file to the server ... 10)DNS settings were correct in ipconfig /all. ... use Group Policy settings to turn off SMB ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: SMB Signing question, SBS2k
    ... > Is the SMB signing issue with XP PRO sp1 and SBS2k still an issue? ... several users complained that copying file to the server ... > 10)DNS settings were correct in ipconfig /all. ... > To work around this problem, use Group Policy settings to turn off SMB ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Event 1030 on member server
    ... The 1030 errors coincide exactly with user MYSERVER$ logging off ... Since MYSERVER$ is a system account, I don't see how SMB ... SMB stand for "Server Message Block" which is an authentication protocol ... What the article is saying is that your server SMB settings might be ...
    (microsoft.public.windows.server.general)
  • Re: Cisco switch upgrade turns XP performance to crap
    ... Put them both on fixed speed and duplex settings or both on auto. ... I would focus on the server that is having the ... There are several incompatibilities related to SMB ... If the cisco switch is fragmenting all the SMB ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Browser Back button problem
    ... If the browser does not re-request the page when he uses the back button, ... settings) there is nothing you can do since no request is re-sent to the ... If the back button is requesting the page from the server and your app ...
    (microsoft.public.dotnet.framework.aspnet.security)