Table of contents
I-363 This value limits the number of times NetBT
broadcasts a query for a name without receiving a response.
Adjusting this value can have a significant effect on the
number of broadcasts on your system.
This value is the interval in milliseconds between broadcasts. The default value is 0x2ee, or 750 decimal. If you make any changes to these values, restart your computer. I-364 If you have a particularly large Lmhosts file and your DNS requests take too long, you can speed up your Lmhosts requests by changing this registry value.
The value is the time, in milliseconds, that elapses before a DNS query of Lmhosts times out.
This value is the time, in milliseconds, that names are cached in the remote name table. The default is 0x927c0 milliseconds, or 600,000 decimal. I-366 If you use WINS and have problems changing IP addresses for certain machines, you may want to check the following registry value.
Setting this value to 1 tells the proxy name server to send a negative response to any broadcast name registration when that name is already registered with WINS or is in the proxy�s local name cache with a different IP address. Setting this value back to 0 lets you change IP addresses again. I-367 If you use a service other than WINS to give you name service information, you can tell NetBT to use it instead of WINS. This registry entry specifies which port NetBT uses. The default is 89, which is the port that the Microsoft WINS Server listens on.
Restart your machine for any changes to take effect. I-368 If WINS name registration takes too long, use this registry value to speed up the interval at which WINS name registration takes place. When it initially registers names, WINS calculates 1/8th of this value and contacts the name server then. After a name is successfully registered, WINS sends a response to the client with the new refresh interval.
Restart WINS for any changes to take effect. I-369 If you are having problems with your network since you installed WINS, you can tweak the following registry entries to help improve performance.
This value sets the number of times that NetBT queries the WINS server before receiving a response.
This value is the time, in milliseconds, NetBT waits before sending the next query in a series of successive queries.
This value is the interval, in milliseconds, that NetBT waits between sending keep-alive packets for a particular session.
This value regulates the size of the name table, which stores local and remote names. Valid values are 1 = small (16 entries), 2 = medium (128 entries) and 3 = large (256 entries). PPTP You just installed PPTP and are afraid that you may have exposed your network to unwanted attacks. Well, no network is 100 percent secure, but these registry entries let you add a little more security to PPTP.
Using these two values, you can effectively control who can access your network via PPTP. If the AuthenticateIncomingCalls value is set to 0, only the clients whose IP addresses match values stored in the PeerClientIPAdresses value are allowed access. If the AuthenticateIncomingCalls value is enabled and no values are contained in the PeerClientIPAddress value, nobody can access your network via PPTP. NWNBLINK I-375 NWNBLink provides many extensions to the Novell NetBios protocol. If you use this protocol in a Microsoft-only shop, you can really speed things up with a few registry parameters.
Changing this parameter tells NWNBLink to use the Microsoft extensions. If NWBLink is communicating with a client using standard Novell NetBIOS protocol, it falls back to the standard version in favor of the extended version.
Windows NT uses this value, which is in milliseconds, when it sends a delayed acknowledgment. You can use this value in conjunction with the AckWindow value, below, to adjust the frequency at which Windows NT must acknowledge frames it is sent. The default value is 250 milliseconds; the value can range from 0 to 65535.
This value controls the number of frames that are received before an acknowledgment is sent. If you have two computers, one on a fast network and the other on a slow link, adjusting this value can increase throughput. Conversely, if both computers are on a fast link, you can turn off this function by setting the value to 0. You can also let Windows NT determine this value dynamically using the AckWindowThreshold value, below. The default value is 2 and represents the number of frames. The range is 0 to 65535.
This value, in milliseconds, dynamically determines whether it is necessary to send automatic acknowledgments. The determination is based on round-trip time. If this value is set to 0, the NWNBLink uses the AckWindows entry. The default is 500 milliseconds; the range is 0 to 65535.
Enabling NWNBLink�s ability to piggyback acknowledgments can increase your overall network performance if you participate in two-way NetBIOS traffic on your network. If you set this value to 1, NWNBLink can piggyback acknowledgments when it detects the end of a message. If this value is set to 0, NWNBLink waits the number of milliseconds set in the AckDelayTime before it sends an acknowledgment.
This value determines how many frames the receiver handles at one time. This value is generally set at session initialization to tell the sender the limit of frames it can send at a time. Altering this value can increase throughput and performance. I-381 In addition to Microsoft extensions to NetBIOS, additional parameters can help improve network performance and work with either standard Novell NetBIOS or NWNBLink (Microsoft Extensions to Novell NetBIOS.) Here are a few of these parameters.
This value is the interval, in 500-millisecond increments, that Windows NT waits between sending find-name requests. Depending on the speed and congestion of your network, you may want to increase the value to decrease overall network broadcasts.
Use this value to determine the number of times a particular broadcast is sent. Increasing this value could result in congested networks; however, certain slower links may require it.
This value alters the behavior of broadcast packets the NWNBLink protocol sends. If the value is 1, NWNBLink uses Novell-style WAN broadcasts. If you are using the BroadcastCount or BroadcastTimeout registry values, you must set this parameter to 0. I-384 The next two values determine how Windows NT handles connection probes. The initiator of a session sends connection probes when a remote connection to a machine fails. Adjust these parameters according to your network speed and congestion.
This value sets the total number of times that Windows NT sends a connection probe. The default is 5; valid values range from 1 to 65,535.
This value dictates how long Windows NT waits between sending connection probes. The default is five 500-millisecond intervals, or 2.5 seconds. Changing this parameter can affect overall network congestion.
This value is used in conjunction with the RetransmitMax parameter, below. Changing this value can greatly reduce the amount of traffic on your network by delaying the interval that a sender waits before resending data. The default value (in 500-millisecond intervals) is 1; change it to 2 to reduce traffic.
This value governs how many times a computer retransmits data before it treats the network path as a bad path. As you can imagine, a slow link requires more time than a faster one. You can tune this value accordingly. I-388 If you have applications that use keep-alive packets, these two registry entries can give you some measure of control over how often NWNBLink sends this type of traffic over your servers and workstations. Fine-tuning this parameter helps reduce network congestion. Using these two values in tandem really helps you control keep-alive traffic.
This value determines how many times a session-alive frame is sent before the initiator gives up on the receiving computer.
This registry value is very important. It determines how often session-alive frames are sent. The value is the number of 500-millisecond blocks it waits before sending a new session-alive frame. NWLINK I-390 These registry parameters let you tweak IPX/SPX. One way to think of it is that you can use these entries to manipulate the actual network adapters that NWLink is bound to. If you are troubleshooting the network adapter running NWLink, this is the place to be.
This value controls the largest frame size that the network adapter allows. If the value is set to 0, NWLink obtains this value from the network it is running on. Otherwise, you may set a limit that the adapter doesn�t support. This setup can be particularly useful if you are on a fast network and the station you are talking with is on a slower connection.
If this value is set to 0, NWLink gets the value from the network it is currently running on. For those of you who were or are NetWare administrators, this value sets the internal IPX network number. The value is stored in hexadecimal and is 8 hex characters long; for example, AAAABEEF. I-392 NWLink supports five different packet types. If you need to set the specific packet type for an adapter, this registry parameter lets you specify the packet types for each adapter.
Valid values are
I-393 The next two values control the routing information protocol (RIP) as it pertains to NWLink. NWLink uses RIP primarily to keep a list of remote machine names that it can use for name resolution. The list can affect the speed at which your computer can locate other computers on the network.
This value determines how many minutes NWLink waits before requesting a RIP update for a particular entry. The value is reset when a valid RIP announcement is received. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Page: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 |
next page 
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||