Currently at a loss. My Windows7 systems (optiplex, various models) are failing to log in to my Novell network. They report that they can't find the tree. And they can't find anything since there is no IP address from the dhcp (a non-Windows dhcp provider) side of the tracks.
What is happening is that once an address is not provided, the onboard Broadcom NIC is DISABLED. I can go into device manager and enable the NIC, then I can manually log in and things are fine, until the next reboot.
These systems are in classrooms and labs, and are frozen to keep students from monkeying with them. Every morning, they are returned to their former condition. When they wake up each morning, some days the NIC and dhcp processes and network login work fine, some days they do not.
Giving a static address to the desk top in my test world works, but that is not an option here. Somehow the dhcp process on the client needs to work every day, every time.
Updated the Broadcom driver, checked the power management settings for the NIC, turned off the firewall, even disabled the deep freezing on my test systems.
At this point, any ideas would be welcomed, I'm all out.
Loren Carter, Montgomery College
What network number are the various frame types bound to?
When you install Client Service on a computer running Windows 2000 Professional, the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol is automatically installed.
Figure 24.5 shows the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol dialog box.
Figure 24.5 NWLink IPX/SPX/NetBIOS Compatible Transport Protocol Dialog Box
The internal network number is used for internal routing purposes when the computer running Windows 2000 is also hosting IPX services. When calculating the best possible route for transmitting packets to a specified computer, multiple routes with the same route metrics can present ambiguity to computer hosts. When you specify a unique internal network number, you create a virtual network inside the computer. This allows for a singular optimum path from the network to the services running on the computer.
Generally, you do not need to change the internal network number. For more information about the internal network number, see IPX Routing in the Internetworking Guide .
To change the internal network number
In Control Panel, double-click Network and Dial-up Connections .
Right-click a local area connection, and then click Properties .
On the General tab, click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol , and then click Properties .
Type a value in the Internal Network Number box, and then click OK .
NWLink IPX/SPX/NetBIOS-Compatible Transport Protocol supports the frame types shown in Table 24.4.
Table 24.4 Supported Frame Types
Supported Frame Types
Ethernet II, 802.2, 802.3, 802.2 SNAP
802.5 and 802.5 Subnet Access Protocol (SNAP)
802.2 and SNAP
Frame types define packet formats used by the different network types.
During the Auto Detect process, NWLink tries each available frame type in the list for the associated medium access type. For example, on an Ethernet network, Ethernet 802.2, Ethernet 802.3, Ethernet II, and Ethernet SNAP are tested to see which frame types NWLink can communicate with. When NWLink receives a response from a NetWare server with one of the frame types, it also receives the network number associated with the frame type for the network segment where the client resides. NWLink then rebinds using the frame types from which it received responses.
The externalnetwork number is a unique number which represents a specific network segment and associated frame type. All computers on the same network segment that use a particular frame type must have the same external network number, which must be unique for each network segment.
The IPX frame type and network number are set during the initial NetWare server configuration. The Windows 2000 Professional NWLink Auto Detect feature then detects the frame type and network number that was configured on the NetWare servers. NWLink Auto Detect is the recommended option for configuring both the network number and the frame type.
Occasionally, Auto Detect selects an inappropriate network number and frame type combination for the adapter. Because Auto Detect uses the responses it receives from computers on the same network segment, Auto Detect might select an incorrect frame type and network number if computers responded with incorrect values. This is usually caused by an incorrect manual setting on one or more computers on the network.
If the Auto Detect feature selects an inappropriate frame type and network number for a particular adapter, you can manually reset an NWLink frame type or network number for that particular adapter. The frame type and network number on Windows 2000 Professional need to match the frame type and network number configured on the NetWare server. You can specify a frame type and network number of 00000000, so that the network number of the network segment is automatically detected. To manually determine the frame type and network number set on the server, inspect the Autoexec.ncf file, or at the command prompt, type:
In the following excerpt from an Autoexec.ncf file, the frame type is Ethernet 802.2 and the network number is set to 17216720.
load c:\EPRO port=300 int=5 FRAME=ETHERNET_802.2
bind IPX to EPRO net=17216720
To manually determine the frame type and network number set on a computer running Windows 2000, carry out the ipxroute config command at the command prompt. Figure 24.6 illustrates the resulting screen.
Figure 24.6 Frame Type Displayed in the Command-Line Interface
The network number, 17216720, and the frame type, Ethernet 802.2, in the
IPXROUTE CONFIG display screen correspond to the settings in the Autoexec.ncf file.
In the environment here, IPX/SPX is long gone. We are totally a TCP/IP network.
The WinXP systems are good, but the Windows7 systems are the ones having problems obtaining their IP address.