For whatever it's worth, I've noticed the following when using
Unattended 4.6 under Windows Server 2003 Standard.
The following Group Policy affected Unattended's initial attempt to
connect to the Install share on the server:
Windows Settings / Security Settings / Local Policies / Security Options
* Microsoft Network Server: Digitally sign communications (always)
* Microsoft Network Server: Digitally sign communications (if
client agrees)
If either of these were enabled, Unattended 4.6 was unable to connect
via SMB, and could only connect via CIFS if the server's fully qualified
domain name (server.example.com.au) was provided rather than simply its
hostname (server). Setting both to disabled allowed Unattended 4.6 to
connect via SMB normally.
I didn't find this mentioned anywhere (that I looked), so here it is.
Regards,
Shane Curtis
--
Tech Support. Mobile 0439-415181 and Email [EMAIL PROTECTED]
Part/T: Walkervale State School, Burnett Heads State School
Casual: Gin Gin State School, Woongarra State School
Elsewhere as able.
Unless explicitly attributed, the opinions expressed in this message do not
necessarily represent the official position or opinions of the State of
Queensland or the Queensland Department of Education.
Whilst all care has been taken, the Department of Education disclaims all
liability for loss or damage to person or property arising from this message
being infected by computer virus or other contamination.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
unattended-info mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unattended-info
