SMB Scan failure after Windows Server 2008/2003 Auto Updates

[seahunter]

I've run into this failure 3 times over the last month on several different MFP's (Aficio C2500,MP2510); formerly working scan to network folder on Win 2003 & Win 2008 server fails after Windows auto updates are applied, error code on panel is "Path not found". The fix in all three cases was to change UNC paths in address book to \\192.168.x.x\scan-path from it's original, \\server-hostname\scan-path. I applied all firmware updates to machines yet was still unable to scan to \\server-hostname\scan-path and, in the end, had to leave the UNC paths with the IP address instead of hostname to keep the scanning functionality for the customer. As they are statically assigned server boxes, this workaround is acceptable but I would like to figure out exactly which update is causing this function loss. Does anyone have any insight into this problem?

[n25an]

Re: SMB Scan failure after Windows Server 2008/2003 Auto Updates

you broke your dns...
consult the link below...
MS Update Breaks External DNS again

[seahunter]

Re: SMB Scan failure after Windows Server 2008/2003 Auto Updates

Thanks for the reply. This is internal hostname resolution though, no need for external nameservers to query local netbios/hostnames. These are boxes running standalone workstations, not domain members, requiring dns only for FQDN resolution outside their gateways. It must be something else.

[jmaister]

Re: SMB Scan failure after Windows Server 2008/2003 Auto Updates

I dont trust name and dns anymore, IP all the way.(not saying ip is bullet proof however)

Drove less as result of it.

edit: can I suggest using wireshark? run one at the recieving end with the path \\hostname\path, scan one file, see what it captures.

[seahunter]

Re: SMB Scan failure after Windows Server 2008/2003 Auto Updates

Yeah it's not DNS. There IS no local dns. The only nameservers configured are the ISP external ones which would not be resolving names on a local subnet (and email scanning is working fine so DNS MUST be working) These are Hybrid Nodes so a netbios name broadcast on the local subnet would be configured as one of their resolution steps. Somehow this is breaking. If this happened once I would disregard but three times at three different customer sites?

IP is great but most of these mid to large offices are using DHCP internally so a configured host/ip address could change resulting in scan failures to local desktops. I've used wireshark on other problems, maybe I'll try it.

[NSD]

Re: SMB Scan failure after Windows Server 2008/2003 Auto Updates

If there is no local DNS then the network is not setup correctly.
If there is a server on site then that should ALWAYS be the DNS server.
If there is no server then the Router should be the DNS server. The workstations should not be sending all DNS queries externally.

However, to get around your issue where then is no local DNS server just set the DNS server in the copiers network settings to the address of the router and this will usually work fine. The only exception is the very latest version of Windows7 which for some machines (OKI - NCB3, Lexmark 5.10) require a firmware update.