Novell 4.11 p/ Windows 2000

[Everton]

Olá Galera

Gostaria de saber o que devo fazer, se realmente preciso mudar algo no sistema, e se tem alguns truques para configurar o servidor do windows 2000, pois uso a novell 4.11 a 6 anos e nunca tive problemas, gostaria de saber algumas opniões e experiencias dos colegas. obrigado.

Há só um detalhe, estou trocando da novell para o windows 2000 nos crientes novos, pois preciso de alguns recursos do windows, vou trabalhar com os dois.

[simplicio]

Amigo ! fique onde está agora ! lembre-se rosto bonitinho nao é um anjinho !! Pode até parecer !!

A Novell dá um show no Windows 2000 em todos os aspectos que vc imaginar ! (servidor de arquivos, DNS,servidor de impressao, etc.. :? :? :? )Prova disso é a Novell ainda é lider em pequenas redes nos EUA, se eles nao deram conta de lá, vai fazer alguma coisa por vc aqui !!??

Só pra ter um idéia, tente ligar no suporte microsoft !!!

Abraços !!

[Clipper]

Eu troquei o servidor Novell por Linux (Kurumin) com Samba e estou satisfeito com o desempenho, apesar de reconhecer que o Novell tem muitos recursos que o Samba não dispõe (porém não estão me fazendo falta), troquei por questão de licença.

Com certeza os 2 são bem melhores que qualquer versão do Windows.

E olha que eu estou usando o Kurumin que não é recomendado para servidor, dizem que show mesmo é o Red Hat, o Conectiva e o Slackware, mas como era minha primeira vez optei pelo Kurumin por ser super fácil, pretendo logo que puder mudar para o Red Hat ou Conectiva.

Ps. Estou usando 10 terminais burros (sem hd), 1 terminal com Windows XP e 1 com Windows 98 pendurados no servidor.

O Servidor tem a seguinte configuração :

Duron 1.100 Ghz - HD 20 GB - 256 MB RAM

Até logo.

Marcelo

[Dudu_XBase]

Opa utilizo novell há mtos anos.
Só mesmo para informação a Novell utiliza uma FAT especial denominada Turbo FAT vc poderá desabilitá-la para ganhar mais segurança caso vc use dbfs mto grandes e esteja tendo problemas com corrompimentos.

// Mais INformações
http://support.novell.com/cgi-bin/searc ... 960009.htm


E achei mais dicas inclusive esta que citei...esta em inglês...

Novell Netware Networks (4.x/5.x/6.x and higher)

Important settings/troubleshooting tips when using this OS:

1. Use NOVELL network drivers only. The Microsoft Windows workstations ('98,NT,2000,XP) must be using the latest Novell client drivers provided by Novell (version 3.01 or higher). DO NOT USE the provided Microsoft drivers to connect to a NOVELL network ever!

As of this writing (May 2004), the latest version is v4.9 SP 1a for Windows NT/2000/XP.
You can obtain the latest driver at : http://www.novell.com/download/
Select "Novell Client v4.9 on Windows NT/2000/XP (English)"

Note: Keep in mind that reinstalling a different redirector resets the Advanced Settings to their predefined defaults. Therefore, do not forget to change the Advanced Settings to the recommended values if necessary
Novell Technical Support recommends the following advanced settings to ensure data reliability. Keep in mind that these settings may affect performance, but are necessary to ensure that file integrity is maintained. The Advanced Settings are located on the Multi-Tabbed Properties Dialog.

File Caching = 0 (OFF)
File Commit = 1 (ON)
Large Internet Packets = 0 (OFF)
Burst Mode = 0 (OFF)

2. Make sure your Server Software is up-to-date. Make sure that the latest Support Pack (SP) is installed. As of this writing (May 2004), the latest versions of NetWare servers are:
Server O/S Latest Support Pack
NetWare Ver. 6.5 SP1.1
NetWare Ver. 6.0 SP4
NetWare Ver. 5.1 SP7
NetWare Ver. 4.2 SP9

To determine which Support Pack is installed on a Novell server:

* From the System Console command prompt, type Version. The NetWare Server version and Support Pack will be shown.

Note: Support for versions of Novell Netware not listed above are not supported by Intellisoft.

3. Disable TURBO FAT feature. By default, Novell uses a special File Allocation Table feature called TURBO FAT to improve performance. However, there have been data corruption problems caused by the use of this TURBO FAT feature of Novell. The corruption occurs while the file is in the server's memory. When the file is modified by an application and rewritten to the server's hard disk, the corruption is introduced. Novell's Technical Information Document 10064734, "How to Disable TurboFat", reports that "The problem is typically seen on NetWare 4.10, 4.11, 5.0, 5.1 and 6.0 file servers with database applications which use large files." The definition of a "large file" is somewhat subjective because it depends on how the hard drive was formatted and the file block size.

The aforementioned Novell article includes instructions to download a Novell patch that will disable this feature. The patch includes files named TURBODIS.NLM and TDIS600.NLM that when installed will disable the TURBO FAT feature.

Because many data files in our software can be considered large, such as the customer file, transaction file, payment file, etc., we STRONGLY recommend downloading this Novell patch and disabling this feature.

Additional details regarding TURBO FAT can be found in the following Novell Technical Information Documents (TIDs) at support.novell.com:

* 2960009 - TURBODIS.NLM to prevent database corruption
* 10064734 - How to Disable NetWare Turbo Fat
* 10062567 - Effects of applying TURBODIS.NLM
* 10012238 - Database Rebuilds occurring on a nightly basis
* 10052321 - TurboFat on NetWare 5 and cc:Mail Database Corruption

4. Disable Opportunistic Locking. Novell NetWare also includes an Opportunistic Locking feature. We recommend that Opportunistic Locking be DISABLED at the Novell NetWare File Server. This applies to servers running under Version 5.0 SP5, Version 5.1 SP2, or later.

This setting can be disabled by:

* editing the AUTOEXEC.NCF file (system directory) or the STARTUP.NCF file (DOS partition); or
* typing the command at the command line of the File Server.

The command to disable the setting is the same regardless of which method is used to implement it. The command is:

SET CLIENT FILE CACHING ENABLED = OFF

We recommend editing the AUTOEXEC.NCF file, which requires rebooting the server after adding the command. However, the command line method can be used temporarily until it is more convenient to reboot the server.

5. If program performance seems unusually slow...
A. Certain older/outdated versions of anti-virus software applications have been known to cause poor network performance and also interfere with the proper operation of ManageMore. Consider temporarily removing the anti-virus program from all of your computers to determine if this is the root of the problem.
B. Some firewall software applications have been known to cause poor network performance and also interfere with the proper operation of ManageMore. Consider temporarily removing the firewall software from all of your computers to determine if this is the root of the problem.
C. It is strongly recommended that you download Novell’s latest service patches for the operating system you own. Visit www.novell.com for the latest patches.
D. You may need to check the Browse Master feature which is enabled by default when using “File and Printer sharing for Microsoft Networks…”. This setting has been known to occasionally cause poor network performance. When using Windows ’98, the setting is located under Network Neighborhood… Properties… File and Printer Sharing for Microsoft Networks… Properties Button… The Browse Master feature should be disabled on all computers except the file server.


6. Synchronize your dates on the network. It is strongly recommended that your network has been setup to synchronize all workstations with the date/time of your Novell Server. This involves the use of a command “NET TIME” in each workstation logon script. Consult with your network administrator on this issue.

7. If you are still having problems... it is always good practice to make sure that all your workstations/servers are using the latest software drivers for your network cards and the latest service packs for your operating system. We strongly recommend using quality network cards (like 3COM or INTEL) to reduce your chances of data packet loss, corruption, and poor performance.

[rrfsistemas]

Olá Everton !

Fiz essa mudançca a muito tempo. Hoje o Win Server 2000 e não tenho problemas com corrompimentos, desde que o servidor esteja configurado corretamente

Lhe dou uma dica : qdo insalar o servidor Win crie regras para um servidor de domínios e utilize o sistema de fat32 em uma partição separada, isto se o seu caso for trabalhar com tabelas separadas (dbfs).

Até :xau