|
General System Registry Secrets Table of contents |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This value controls the length of time a current RIP cache entry is valid. Modifying this parameter with the RipAgeTime parameter lets you reduce your overall RIP-based traffic on a heavily congested network. I-395 If you have many computers and routers on your LAN, you may want to consider source-routing with your NWLink protocol. NWLink has several registry entries that give you some control over how it uses source-routing. The following four values control the bulk of source-routing features.
If this value is 0, the broadcast is transmitted to the single-route broadcast. If the value is set to 1, the all-routes broadcast is used. This setting can make a huge difference in network overhead.
This value is very similar to the SourceRouteBcast value; it affects those broadcasts destined for machines that are not in the route table. If NWLink finds the computer in the route table, it uses that route; otherwise, if the value is 0, it uses the single-route broadcast. If the value is 1, NWLink uses the all-routes broadcast.
This value specifies whether source-routing should be used on a Token-Ring adapter. This value pertains only to Token-Ring adapters.
This value affects multicast addresses. If the value is 0, NWLink uses the single-route broadcast. If the value is 1, NWLink uses the all-routes broadcast. I-399 These next seven values affect IPX/SPX globally. The values under the adapters section affect only a specific card; these values work for the whole NWLink transport.
This value sets the number of packets the receiving node can receive at a time. The SPX protocol uses the allocation field of the SPX packet to inform remote nodes of the available window size. This value sets the allocation field in the SPX packet. I-400 These next two values pertain to RIP on an IPX/SPX network. Altering these settings affects all adapters running NWLink.
This value determines how many times RIP tries to find a route on a network before it declares the route unusable. Depending on network traffic levels, adjusting this value can increase the likelihood that RIP finds routes.
This value works in conjunction with RipCount to determine in 500-millisecond intervals how long RIP waits between sending request packets for a particular route.
This value determines how long NWLink tries to connect to a remote machine. If SPX does not get a response within the allotted number of tries, an error occurs. If you have a heavily congested network, tuning this parameter and the ConnectionTimeout parameter below may help you reduce connection timeouts.
This value is how many 500-millisecond intervals NWLink waits between sending connection probes. A value of 2 represents 1 second. By increasing this value and decreasing the ConnectionTimeout value, you can reduce congestion and still maintain your connections.
This value is how many 500-millisecond intervals NWLink waits before sending a keep-alive packet to a remote station to verify that the SPX connection is still functioning.
This value is the number of keep-alive status requests that are sent. If you have long-term connections that are often idle for much of their connect life, you may want to tweak these parameters accordingly. REMOTE ACCESS SERVER (RAS) I-406 If you share phone lines with voice or fax and need to change the number of rings RAS waits before it answers the phone, change this registry parameter.
If you try to set the value to a number greater than 20, the default value (1) is used. Restart RAS for this value to take effect. This registry entry only affects UNIMODEM devices. I-407 From time to time it is necessary to exclude certain dial addresses from the service. Basically, changing this value lets you hide certain RAS addresses without deleting them. If your RAS dialer is set up to choose alternates when it encounters a busy signal, you can appreciate the convenience of this feature. To exclude an address, add it under the following registry value.
All addresses are case sensitive. This registry value is automatically created the first time you run AutoDial. After it is created, AutoDial does not modify it; you add the addresses you want to deactivate for the AutoDial service. I-408 If you are experiencing a slight delay after you type your credentials in the �Connecting to� dialog box, you may have accumulated too many cached passwords. This registry entry lets you disable the caching feature.
Add this value under the Parameters key:
Changing this value to 1 effectively clears all cached passwords and prevents RAS from caching any further phonebook entries. The default value is 0, which enables the password-caching feature. Restart your machine for these values to take effect. I-409 Logging off closes all RAS connections. If you have a remote machine connected to your corporate LAN and multiple people use it, you might want to keep RAS connections open even when a person logs out. This registry entry keeps RAS connections even if you log out.
Add this value under the Winlogon key:
Restart the RAS service for this change to take effect. I-410 You can control the time your RAS server�s modem waits before it calls back and authenticates a remote user. This registry entry lets you specify a value between 1 and 255 seconds.
The default is 12 seconds. Restart RAS for these values to take effect. I-411 Are your non-Windows NT and non-Windows 95 clients having trouble connecting to your Windows NT RAS server? If you told the NT server to use clear-text authentication, but you�re still having trouble, try setting these registry parameters to help solve your problem.
Restart Windows NT for these changes to take effect. I-413 Do you want the �Logon Using Dialup Networking� checkbox in the logon screen to be checked by default? This registry entry tells Windows NT to use dialup networking for logon by default.
Restart Windows NT for these changes to take effect. I-414 VanJacobsen (VJ) compression confuses some older dial-up clients. You can�t disable VJ compression on the client, so use these entries to disable it on the server.
Add the following value under the Parameters key:
I-415 You must also change this registry entry to disable VJ compression:
You must restart RAS for this change to take effect. I-416 If you want to keep track of who is using your RAS server by having RAS write in the Event Log, change this entry.
Add the following value under the Parameters key:
I-417 You recently established service with an ISP. The problem is, you can ping the LAN before you dial up your ISP, but not after. Modify these registry entries to fix this problem.
Add the following value under the IPCP key:
This value controls the logging action of PPP events that the RAS server handles. A value of 1 enables logging and 0, the default, disables logging. I-419 If you recently added Internet access to your LAN via the RAS server and can get out just fine but everything coming back stops at the default gateway machine, then change this registry entry.
Add the following value under the Parameters key:
Now all your Internet data will make it back to the right machine. I-420 Are you having problems with your dial-up connections? Are you getting more retries than you should? You may need to enable the FIFO buffer on your serial card (if you have one, and you should). In addition, you may want to lower the receive buffer. These registry entries let you govern the size of the FIFO buffer for both receiving and transmitting.
Enable the FIFO buffer by setting this value to 1. Restart the machine and see if this helps. If you still experience problems, try reducing the value of the receive FIFO buffer to 4; if you still have problems, drop it to 1.
This value governs the receive buffer.
This value governs the transmittal buffer. I-423 Have you noticed that your laptop seems to receive files when you�re connected to the corporate Ethernet but chokes when you�re connected at a lesser speed (i.e., on a 28.8 modem connection)? Try modifying this parameter.
Add the following value under the Parameters key:
Generally, slower connections benefit from a higher value; however some RAS connections work better with the value set to around 2768. For maximum efficiency, this value should be an even multiple of the TCP maximum segment size. ROUTING INFORMATION PROTOCOL (RIP) I-424 Does your Windows NT reject host routes or default routes that are broadcast by RIP-enabled routers? These registry entries will fix you right up.
Add the following value under the Parameters key:
The default value is 0. Reboot your machine for these changes to take effect.
Add the following value under the Parameters key:
The default value is 0. Reboot your machine for these changes to take effect. I-426 Do you want to broadcast your default routes to other RIP-enabled routers in your network? Set this registry parameter to enable this function.
Add the following value under the Parameters key:
The default value is 0. Reboot your machine for these changes to take effect. I-427 Do you want to broadcast your host routes to other RIP-enabled routers in your network? Set this registry parameter to enable this feature.
Add the following value under the Parameters key:
The default value is 0. Reboot your machine for these changes to take effect. I-428 By default, any new route information or metric change automatically triggers a RIP update. Do you need to disable this feature? This registry entry shows you how.
Add the following value under the Parameters key:
The default value is 1. Reboot your machine for these changes to take effect. I-429 This value is used in conjunction with the EnableTriggeredUpdates registry entry; it sets the number of seconds between triggered updates.
Add the following value under the Parameters key:
The default value is 5; valid values range from 1 to 86,400 seconds. Reboot your machine for these changes to take effect. I-430 If you have a lot of dynamic routes created on your network, this registry entry may help you increase performance on your network. This value regulates when a route should be designated as a garbage route.
Add the following value under the Parameters key:
The default value is 180; valid values can range from 1 to 259,200 seconds. Reboot your machine for these changes to take effect. I-431 Are garbage routes on your network not removed as quickly as you would like? This registry entry lets you set how often garbage routes are discarded.
Add the following value under the Parameters key:
The default value is 120; valid values can range from 15 to 259,200 seconds (72 hours). Reboot your machine for these changes to take effect. I-432 If you�re trying to debug RIP problems, this registry entry lets you adjust the amount of information RIP records to the logging file.
Add the following value under the Parameters key:
The default value is 1. Valid values are
Restart your computer for these changes to take effect. I-433 Are RIP announcements overloading your network? Do you want to silence periodic updates, yet still send triggered updates and receive all other RIP information? This registry entry suppresses periodic RIP announcements.
Add the following value under the Parameters key:
The default value is 0. Setting the value to 1 suppresses periodic RIP announcements. Restart your machine for changes to take effect. I-434 If you still want to send periodic updates (updates that contain the entire routing table for a given multiprotocol router), but not as often, you can regulate the frequency of the periodic updates with this registry entry.
Add the following value under the Parameters key:
The default value is 30 seconds; valid values range from 15 to 86,400 seconds. Restart your MACHINE for these changes to take effect. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Page: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 |
� | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||