Newsgroup: it.comp.reti.locali
Titolo: Dominio Win 2000 server e XP Professional: apertura e chusura di file in rete

E' un mese che i tecnici a cui ci affidiamo si rompono la testa sul seguente
problema.
File server Win2000 appena reinstallato, pulito, pulito: oltre al S.O. c'è
solo Sql server.
La rete ha un dominio, quindi Active Directory..., no DHCP, gli IP sono
statici.
I client Win2000Pro e i pochi Win98 rimasti non hanno problemi, ma i nuovi
XP Pro (almeno sei con hardware diversificato) manifestano tutti un problema
per noi enorme: l'apertura e la chiusura di file salvati sul server (e solo
di questi) è un vero calvario.
Spesso, molto spesso, MA NON SEMPRE, o si manifestano problemi in apertura
(molte decine di secondi di attesa dopo i quali il file o non si apre
proprio - messaggio: "controllare percorso di rete, nome file, privilegi di
accesso" e altre fregnacce del genere - o si apre in sola lettura come se
fosse occupato da un altro utente, che poi è il medesimo che ha tentato di
aprirlo) oppure i problemi compaiono alla chiusura, nel senso che sul client
il file si chiude regolarmente, ma il server lo "sente" ancora aperto e non
lo rilascia (impossibile rinominarlo, cancellarlo, ecc.) e ciò sino alla
disconnessione del client dal dominio.
L'hardware è a posto, l'antivirus è estraneo al problema (dopo molte prove
sono sicurissimo), il visualizzatore eventi del server non evidenzia nulla,
gli Switch e le porte relative sono ok (ho provato a scambiarle varie
volte). Tutti i client XP si comportano allo stesso modo.
Dopo innumerevoli prove ho il forte sospetto che la grana sia connessa con
l'eliminazione del protocollo NetBeui da XP Pro (che sui client 2000Pro
usiamo ancora per non perdere la mappatura delle unità nelle finestre di
apertura dei file).
Ho attivato il NetBIOS sul TCP/IP e il Wins, ma non è cambiato nulla.
Sembra che il problema peggiori se si utilizza la mappatura delle cartelle
condivise sul server tramite le lettere di unità, ma anche utilizzando solo
le risorse di rete il problema c'è.
Non so più dove sbattere la testa, siamo tutti abituati a lavorare
pesantemente in rete (che però non ha problemi di carico eccessivo):
aiutatemi per favore...
--
GB ego sum
PS: leggendo un po' su groups.google sembra che il problema non sia solo
nostro, ma non ho trovato indicazioni utili.

Tiè, ci ho messo meno del previsto.
Prova, con me ha funzionato.
Ti posto prima un estratto con la soluzione, e sotto l'articolo intero.
------- estratto:
WORKAROUND
To work around this problem, use Group Policy settings to turn off SMB 
signing. To do so, set the Default Domain Controller policy settings to 
Disabled:
Click Start, point to Programs, point to Administrative Tools, and then 
click Active Directory Users and Computers.
Right-click the Domain Controllers organizational unit, and then click 
Properties.
Click the Group Policies tab.
Click Default Domain Controllers Policy, and then click Edit.
Go to the following location:
Computer Configuration\Windows Settings\Security Settings\Local 
Policies\Security Options
If any of the following policy settings are set to Enabled, double click 
the setting, click to select the Define this policy setting check box, 
click Disabled, and then click OK.
NOTE: By default, only one setting is set to Enabled.
Digitally sign client communication (always)
Digitally sign client communication (when possible)
Digitally sign server communication (always)
Digitally sign server communication (when possible)
Close Group Policy editor, click OK, and then quit Active Directory 
Users and Computers.
--------------------- atticolo intero:
  Articolo Microsoft Knowledge Base - 331519
  Network File Errors Occur After You Install Windows XP SP1
The information in this article applies to:
Microsoft Windows 2000 Server SP1
Microsoft Windows 2000 Server SP2
Microsoft Windows 2000 Server SP3
Microsoft Windows 2000 Professional SP1
Microsoft Windows 2000 Professional SP2
Microsoft Windows 2000 Professional SP3
Microsoft Windows XP Professional SP1
This article was previously published under Q331519
SYMPTOMS
After you install Windows XP Service Pack 1 (SP1), you may see a variety 
of errors relating to Windows XP SP1 client computers. These errors may 
include, but are not limited to the following errors:
When you open Microsoft Office files, they are opened as read-only (you 
have to click Save As to save a file).
You cannot copy files.
The file or the network path no longer exists.
Network paths are not accepted by any network provider.
The following event ID messages are logged after you apply Group Policy 
objects (GPOs):
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 2/8/2002
Time: 7:25:40 AM
User: NT AUTHORITY\SYSTEM
Computer: MYCOMPUTER
Description: Windows cannot access the file gpt.ini for GPO
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=lcds,DC=lab 
The file must be present at the location 
\\lcds.lab\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}
(Access is denied) Group Policy processing aborted.
Event Type: Error
Event Source: SceCli
Event Category: None
Event ID: 1030
Date: 2/8/2002
Time: 7:30:46 AM
User: N/A
Computer: MYCOMPUTER
Description: Windows cannot query for the list of Group Policy objects. 
A message that describes the reason for this was previously logged by 
the policy engine.
The following event ID message is logged:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 2/8/2002
Time: 12:30:46 AM
User: N/A
Computer: NT AUTHORITY\SYSTEM
Description: Windows cannot access the file gpt.ini for GPO 
CN={GUID},CN=Policies,CN=System,DC=DOMAIN,DC=com. The file must be 
present at the location 
<\\
domain.com
\SysVol\
domain.com
\Policies\{GUID}\gpt.ini>. (Access is 
denied. ). Group Policy processing aborted.
You receive the following error message when you try to open a file on a 
network share:
Cannot open the File on network share
Make sure a disk is in the drive you specified.
You cannot find the file that you specify, even when you select a file 
from Windows Explorer.
Some files are corrupted.
Generic error messages that indicate errors copying a file or opening a 
file appear at random on the Windows XP SP1 client.
CAUSE
These problems occur because of an incompatibility in Server Message 
Block (SMB) signing between Microsoft Windows 2000 and Windows XP SP1. 
By default, SMB signing is turned on on domain controllers only when 
possible. By default, you only experience this problem when you copy 
files to and from a domain controller. However, if you apply policy 
settings or set registry keys to servers, you may experience problems 
when you copy files to and from a server.
WORKAROUND
To work around this problem, use Group Policy settings to turn off SMB 
signing. To do so, set the Default Domain Controller policy settings to 
Disabled:
Click Start, point to Programs, point to Administrative Tools, and then 
click Active Directory Users and Computers.
Right-click the Domain Controllers organizational unit, and then click 
Properties.
Click the Group Policies tab.
Click Default Domain Controllers Policy, and then click Edit.
Go to the following location:
Computer Configuration\Windows Settings\Security Settings\Local 
Policies\Security Options
If any of the following policy settings are set to Enabled, double click 
the setting, click to select the Define this policy setting check box, 
click Disabled, and then click OK.
NOTE: By default, only one setting is set to Enabled.
Digitally sign client communication (always)
Digitally sign client communication (when possible)
Digitally sign server communication (always)
Digitally sign server communication (when possible)
Close Group Policy editor, click OK, and then quit Active Directory 
Users and Computers.
By default, Group Policy settings are refreshed on domain controllers 
every five minutes. To force the policy settings to be refreshed on 
Windows 2000 immediately, run the following command:
secedit /refreshpolicy machine_policy /enforce
After the settings are applied, restart Windows 2000.
The following list describes the default settings for the Default Domain 
Controllers policy settings:
Digitally sign client communication (always): Not defined
Digitally sign client communication (when possible): Not defined
Digitally sign server communication (always): Not defined
Digitally sign server communication (when possible): Enabled
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products 
that are listed at the beginning of this article.
MORE INFORMATION
For additional information, click the article numbers below to view the 
articles in the Microsoft Knowledge Base:
161372 How to Enable SMB Signing in Windows NT
314494 Group Policies Are Not Applied The Way You Expect; Event ID 1058 
and Event ID 1030 Errors in the Application Log
