jamesclancy
asked on
WINS Resolution Problem
Scenario:
We are runnint Windows NT 4.0 with Exchange Server 5.0. Our Network Protocols are TCP/IP and NetBEUI.
We previously had two subnets (we'll cal them Alpha and Beta) communicating across an ISDN line.
Network Alpha's IP block was: 216.14.26.64-128
Network Beta's IP block was: 216.14.26.1-63
The subnet mask for both networks was: 255.255.255.192
We moved network (Beta) to the same physical network (Alpha) and reassigned DHCP to issue addresses between 216.14.26.1-128 with a subnet mask of 255.255.255.125.
We seem to be able to ping any workstation on the local subnet without problems by using the IP address. However, when we try to ping using NetBios names, many of the workstations don't respond. More importantly, many workstations cannot get their e-mail because their e-mail client registers with Exchange Server using a NetBios name.
By the way, we deleted the WINS server database and added a new one so that it would reconstruct itself.
I cannot figure this out.
We are runnint Windows NT 4.0 with Exchange Server 5.0. Our Network Protocols are TCP/IP and NetBEUI.
We previously had two subnets (we'll cal them Alpha and Beta) communicating across an ISDN line.
Network Alpha's IP block was: 216.14.26.64-128
Network Beta's IP block was: 216.14.26.1-63
The subnet mask for both networks was: 255.255.255.192
We moved network (Beta) to the same physical network (Alpha) and reassigned DHCP to issue addresses between 216.14.26.1-128 with a subnet mask of 255.255.255.125.
We seem to be able to ping any workstation on the local subnet without problems by using the IP address. However, when we try to ping using NetBios names, many of the workstations don't respond. More importantly, many workstations cannot get their e-mail because their e-mail client registers with Exchange Server using a NetBios name.
By the way, we deleted the WINS server database and added a new one so that it would reconstruct itself.
I cannot figure this out.
Your subnet mask is hopefully 255.255.255.128 and not 255.255.255.125 (which could definitely be a reason for the above behavior).
Also, assign addresses from 216.14.26.1 to 126 (127 is broadcast for that subnet and 128 is the subnet address for the next subnet).
Also, assign addresses from 216.14.26.1 to 126 (127 is broadcast for that subnet and 128 is the subnet address for the next subnet).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What IP address does the WINS server have - post up its IPCONFIG /ALL.
What does IPCONFIG /ALL from a failing client say ?
When you say 'PING' using NetBIOS names, what do you mean ?
PING will search for a DNS hostname, not NetBIOS name, althought these can be exactly the same !