![]() ![]() This Registry value is a global IPX setting that isn't RAS specific, so it affects the behavior of IPX on all adapters. Table 2 lists the possible values for this Registry subkey. The second Registry value that affects NetBIOS-over-IPX broadcast traffic is the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NwlnkRip\ Parameters\NetBiosRouting subkey of type REG_DWORD with a default value of 2. Table 1 lists possible values for this setting. The HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\NwlnkIpx\Parameters\DisableDialinNetbios subkey is an IPX-specific value of type REG_DWORD that defaults to 1, which means that RAS broadcasts NetBIOS packets from only remote clients to the internal network and the RAS server, but RAS doesn't forward the packets back to the remote clients. Two Registry entries affect this configuration. To understand these problems, you first need to understand how Windows NT treats RAS clients in NetBIOSover-IPX (i.e., Type 20 packets) broadcast traffic. Several problems are common to IPX-based RAS scenarios. ![]() ![]() ![]() This issue, I discuss the Registry values that affect the behavior of another RAS-supported protocol-NWLink IPX/SPX. In October, I covered NetBEUI-based RAS clients and discussed the RAS NetBIOS gateway, the RAS RemoteListen parameter, and how to modify your RAS server's configuration to extend networking functionality to your RAS clients. Modify your Registry to resolve common IPX-based RAS problems ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |