Troubleshooting with Microsoft - 01 Mar 1997

Novell NetWare Integration

Q: How can I change passwords on a Windows NT File-and-Print Services for NetWare (FPNW) server and a Novell NetWare server at the same time?

You can synchronize passwords on a NetWare server and an FPNW server with the setpass.exe or chgpass.exe program. Before you use setpass.exe or chgpass.exe from an FPNW server Sysvol\Public directory, make sure the password on the NetWare server is the same as the password on the FPNW server. If the passwords are not identical, the FPNW will not ask you to synchronize the password on the NetWare server and the password on the NetWare server will not change.

Q: How can I route IPX on an NT server?

NT IPX internal routing supports LAN-to-LAN routing, forwarding, and NetBIOS packet propagation. IPX has an addressing mechanism to deliver packets to a destination. NT Server 3.51's IPX implementation conforms to the Novell IPX Router specification.

To enable IPX routing, you must install the IPX protocol and Routing Information Protocol (RIP) for IPX. The Service Advertising Protocol (SAP) agent installs automatically when you install RIP. IPX addresses, routes, and switches information packets to move single packets from one location to another in an inter-network (with the help of RIP and SAP).

To enable IPX routing in NT Server 3.51 and NT Server 4.0, follow these steps:

1. For NT Server 3.51, select the NWLink IPX/SPX Compatible Transport in Installed Network Software of Control Panel Network, and click Configure. For NT Server 4.0, select the NWLink IPX/SPX Compatible Transport in the Protocols tab of Control Panel Network, and click Properties.

2. In the NT 3.51 NWLink IPX/SPX Protocol Configuration dialog box, select the Enable RIP Routing check box. In the NT 4.0 NWLINK IPX/SPX Properties, select Enable RIP Routing. When you install RIP, the check box is selected by default.

3. In NT 3.51, choose the Manual Frame Type Detection option, and select the frame type that applies to your network. Click Add for each frame type. In NT 4.0, choose the Manual Frame Type Detection option in the General tab, and select the frame type that applies to your network. Click Add for each frame type.

4. Do not change the Internal Network Number unless no network number is defined for the NT server segment. If the network number is defined, NT Server automatically detects the network number during the boot process. Use ipxroute.exe to determine the network number of your network adapter. For example, type

ipxroute config

For the segment the NT server is connected to, if an administrator has not configured any Novell NetWare servers or an NT server with a network number, you must define a Unique Network Number for that segment. For example, suppose you have an NT 3.51 server with two NICs. The first NIC is connected to an existing Novell network, so you can leave the network number blank. NT server autodetects the network number for that segment. The second NIC is connected to the Microsoft Network, and no IPX network number is defined for this segment. You must then type a unique network number for this segment. Click OK, and quit Network Settings. Shut down the system, and restart NT.

Q: Why can't my clients that run NT Workstation browse Microsoft Network computers on the other side of a router?

Your routers apparently cannot propagate NetBIOS packets across the network. This ability is necessary for NetBIOS to operate in an NWLink environment. NetBIOS provides session-layer services such as packet assembly and disassembly and named addressing for Microsoft's NWLink protocol. NetBIOS, like SPX, also provides guaranteed packet delivery and packet sequencing on the Transport layer.

To propagate packets, the LAN administrator must configure the router to forward IPX packet type 20. Because IPX is a derivative of the Xerox XNS IDP protocol, it follows the Xerox packet types.

Packet type 20 (0x14) identifies a NetBIOS packet and is a propagated packet. The Destination Node field in the IPX header is set to 0xFFFFFFFFFFFF. When a router receives this packet, the router checks the IPX header Packet Type field. If Packet Type is 20 (0x14), the router examines the Transport Control field. If the Transport Control field is more than 8, the router will discard the packet because a type 20 packet is propagated over a maximum of 8 networks. The router then compares the value in the Network Number field with the network number of the segment it received the packet from. If these numbers match, the router discards the packet to prevent sending it over the same segment twice. The router then puts the network number of the segment it received the packet from in the next available Network Number field and increments the Transport Control field before broadcasting the packet to all directly connected network segments not represented in the Network Number fields.

Q: Why can't I see the Remote Access Service (RAS) server in File Manager or from the Network Neighborhood from an NT RAS client?

When you make a Point-to-Point Protocol (PPP) connection with the IPX/SPX Compatible Transport protocol from a RAS client to an NT RAS server only, the RAS server does not appear in the File Manager browse list on the RAS client (even though you have full administrative permission to the RAS server). You can connect properly to the shared resources on the RAS server using File Manager or the MS-DOS Command Prompt (cmd.exe). You must know the specific names of the shared resources in advance.

To view resources on the RAS server, install the NetBEUI protocol in addition to IPX/SPX Compatible Transport protocol. After rebooting and establishing a connection to the remote server, you can browse resources on the server.

Q: Does the FPNW server support Novell's 32-bit client?

The FPNW 4.0 patch supports Novell's Client32 redirector. This enhancement, applied to FPNW 4.0 running on NT Server 4.0, permits Client32-compatible redirectors to see and use services from your NT server. The patch is available on

Q: Why can't I connect to a Novell NetWare 4.x server volume from Windows Explorer on an NT 4.0 workstation configured for the same NetWare Directory Services (NDS) tree?

The NetWare volume might be in a different context from what is configured in NT. The NetWare 4.x-based server volume must be in the same context configured in Gateway Services for NetWare (GSNW). Client Services for NetWare (CSNW), which comes with NT 4.0 Workstation, and GSNW, which comes with NT Server 4.0, allow access to NetWare file-and-print resources from an NT computer. CSNW and GSNW redirect requests to a NetWare Server using NetWare Core Protocols (NCPs). Browsing the NDS tree in Windows Explorer does not change the context of the workstation. To connect to NetWare 4.x servers with different contexts, move the NetWare volume to the NDS context configured in GSNW or CSNW or use a login script to change the NDS context to reflect the NetWare 4.x volume's location.

Q: Why can't I connect to NetWare 4.x servers using GSNW on an NT server?

When you try to set up GSNW in Bindery Mode from an NT server to a Novell 4.x server, you sometimes get the error message, "Access denied." The probable cause of this error is that you are trying to connect to a volume on the Novell 4.x server that is running outside the bindery emulation context.

NDS is part of the NetWare 4.x OS. NDS regulates access to network information, resources, and services.

NT GSNW 3.50 and 3.51 servers cannot set up a gateway to a volume in an NDS branch. NT can set up a gateway to a volume in a branch only with bindery emulation. To check for bindery emulation volumes, type


at the NetWare 4.x server's System Console. This command gives you server information, and on the bottom of the screen, a section titled Bindery Context tells you which branch is running in bindery emulation. The NTGATEWAY group must be an object under this branch. The NT server user account must also be an object under this branch. The rest of the GSNW setup is the same as for NetWare 3.x servers. To complete setup, read Chapter 13 of the Networking Supplement of the Windows NT Server documentation or Server Books Online about Services for NetWare Networks, which is included with Windows NT Server CD.

Q: Why can't I copy files from a NetWare server on a Fiber Distributed Data Interface (FDDI) ring to an NT server?

On your NT computer, you can view files on a Novell NetWare server from File Manager, but you can't open these files or copy them to a local drive. If you try to open a file, the Event Viewer shows the following error:

Event Id 8007: The Microsoft client service for NetWare redirector has timed out a request to

These symptoms occur when you use NT on an Ethernet network segment with CSNW or GSNW installed and attached to a Novell NetWare server connected to an FDDI ring.

To work around this problem, decrease the packet size from 4202 to 1514 on the NetWare server or set MaxPktSize to 1012 on the NT server. Follow these procedures to add the parameter in the Registry. (Warning: If you use Registry Editor incorrectly, you can cause serious, systemwide problems that can require you to reinstall NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.)

1. Run Registry Editor (regedt32.exe).

2. From the HKEY_LOCAL_MACHINE subtree, go to \System\CurrentControlSet\Services\NwlnkIpx\NetConfig\Driver

3. Edit value MaxPktSize:REG_DWORD: 1012 (decimal)


Q: Can I use Microsoft Dynamic Host Configuration Protocol (DHCP) service on a physical segment with multiple IP subnets?

Many people run multiple IP subnets on one physical LAN segment, a configuration called multinetting. Versions of NT DHCP Server before NT 4.0 Service Pack 2 (SP2) cannot assign addresses from more than one scope to a given physical subnet. Typically, the network administrator had to insert additional NICs on the server and address each NIC to a given logical IP subnet. This procedure involves additional and otherwise unnecessary hardware, so Microsoft developed and implemented a new solution in SP2.

The solution, superscoping, supports DHCP clients on local networks that have more than one subnet on a physical network. Superscopes also support DHCP clients on the remote side of bootp relay agents, when the network has multiple logical subnets on one physical network.

The DHCP server will let you group different ranges of IP addresses (different scopes) into one superscope. For more information about superscopes, see the Microsoft Knowledge Base, article Q161571 at

Q: Can the Domain Name System (DNS) resolve IP addresses to host names (i.e., perform reverse lookup)?

Most of the functionality of a DNS server works to resolve a given host name by finding the host's IP address. However, you will also want the ability to give the DNS server an IP address and get a host name back. You can create a reverse lookup zone file in addition to the zone file for your domain. The name of the zone is your network or subnet address inverted, with appended to the end. For example, if you have Class C address, create a primary zone Now when you add a host entry with IP address 192.16.1.X to your domain zone file, you can click Create Associated PTR Record. This command automatically creates a PTR record in your zone. Now a reverse DNS lookup for this host will be successful. If you want to do reverse lookup for names resolved by a DNS-to-WINS lookup, check Use WINS Reverse Lookup on the WINS Reverse Lookup tab under Properties for your reverse domain. When you check this option, DNS uses a NetBIOS adapter status to resolve names because WINS does not support reverse lookups.

Macintosh and NT

Q: I use my new NT 4.0 server as a file server for my Macintosh and PC clients, and now my Macintosh clients have trouble opening their files. Macintosh users claim to see the files as a generic PC icon. When I checked the files with the Macintosh ResEdit utility, I found that the file Type is TEXT and Creator is LMAN. What can I do to solve this problem?

Microsoft's Knowledge Base article, Q159205, SFM file Type and Creator Properties Invalid, tackles this problem. When the PC client opens and saves the file, the resource fork is lost. Microsoft has updated the sfmsvc.sys and sfmsrv.sys in NT 4.0 SP2 to keep the resource fork.

Corrections to this Article:

  • "Troubleshooting with Microsoft: included an incorrect Web address in the section on DNS and DHCP. The correct URL is
Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.