Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Question from wallacemd on Jun 20 at 10:00 AM Greetings All,
First post...probably not in the right group. Sorry.
We're running SAP on Windows boxes hitting DB2 for z/OS.
The SAP/Windows instances talk to z/OS SMB shares for central file services (dir_exe_root, dir_ct_*, etc.) as well as central services instances.
This past weekend, our Windows servers, on schedule, applied MS KB 3161949 (WPAD sec update). This caused our Windows servers to lose connection to the SMB shares on z/OS. As a result, the Windows/SAP services (SAPSID_NR) failed to start; hence, the instance would not come up.
Uninstalling MS KB 3161949 is only a temporary fix.
Another work-around is to enable NetBIOS over TCP/IP and add explicit z/OS hostname entries in the lmhosts file on each Windows server. This seems to work.
Calls from the Windows boxes to the z/OS host SMB shares (\\zos-host\smbshare) will work if you add FQDN to the hostname (\\zos-host.fully.qual.dom\smbshare). But this means a ton of mods in your SAP config (java config files, profile files, who knows where else...).
I don't know what the permanent fix is; if there is one. Likely the lmhosts work-around will have to do.
Mike
| Reply to this email to post your response. __.____._ |    _.____.__ |
