Discussion Locked

Can't connect W98 PC to NT 4.0 server

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a NT 4.0 PDC server running and I want to connect a Win98 to it via Ethernet.
Both PC's have a IP address (100.0.0.100 and 100.0.0.101, netmask 255.255.255.0)
On the Win98 PC I configured the client for Microsoft Networks that it should logn to windows NT domain 'EMS-DOMAIN' (domain name of the NT 4.0 server)
But when the win98 PC starts it can't find the domain and I also can't ping the server and from the server I can't ping the win98PC.
I checked my ethernet hub and cabling with another win98PC. They can connect to eachother using a workgroup and also TCP/IP but with the NT server it's not working.
Who can help me with this.

Thanks and regards,

Ruud Kruyt

17 replies

by avachon

Hi, did you add the 98 machine to server manager on your nt PDC? If not, add it. Also, check the identification tab on the network applet to be sure it is set to the domain (verify this even though you entered the domain name under properties for microsoft networks. Finally, type in winipcfg at the command prompt to see check connectivity status. You also could set up wins on the nt server (or use lmhosts file) for name resolution (once the connectivity problem is solved). One of these should clear the problem, but if not, run diagnostics on your nic card. Hope these suggestions help you.

by rws

From the information you've provided, it appears that you are having a communication issue. If the server and PC can't ping, they can't communicate. Can anyone else connect to the server? If yes, then the problem is with the PC and/or the physical layer components connecting it to the server. Check the TCP/IP settings. Can the PC ping 127.0.0.1? Yes, then the stack works. No then remove and reinstall the TCP/IP stack. Can the PC ping itself? No, NIC is probably bad. Yes, then check cabling to hub/switch. Do you get a link lite on both the NIC and the hub/switvh port? etc.........

by adriatico

definitely sounds like a comms issue. if the two win98 machines can talk to eachother, and neither can talk to the server, then concentrate on the server and it's connections. could be the card, could be the cable or even it's port on the ethernethub. and double check it's settings again.

by alin selicean

Hi ! Seems that you have a communication issue.

First you should check if the TCP/IP protocol is properly installed. Do this by ping-ing 127.0.0.1 on both machines. If you get a reply on both machines, TCP/IP is OK.

Second, check if other workstations are connecting to that PDC. If so, the server should be working fine and issue should be the W98 workstation.

Third, check that you have the latest patch for TCP/IP available on Microsoft's site. I know that for Win9x family there is a patch for TCP/IP protocol (version 2 if I remember crorectly - WinSock 2). Apply this patch if necessary.

Fourth, on Control Panel on W98, double-click Network applet and make sure you don't have anything else than Client for Microsoft Networks, TCP/IP protocol and desired netwrok adapter. Remove anything extra, but if you plan to use them, write them down for later installments.

PING in the following order: 127.0.0.1, network adapter and server. If one fails, that should be the problem.

Good luck.

by ustutz

1. Do not add Windows 98 machines in the Server Manager Applet - that is only for NT boxes (workstation or servers).

After checking network connectivity from the server to the PCs:

2. Make sure you do not use workgroups in an NT domain. Workgroups and Domains do not mix, even though it looks like they should. On Windows 98/95 boxes set the "workgroup" in the network properties identification tab to the domain name.

3. Set up either WINS or LMHOSTS files. For WINS, make the PDC the primary WINS server, and point BOTH WINS entries (primary and secondary) to it's own IP address. On the PC, make sure you have two WINS entries (even if you run only one server, in that case make both entries the same).

For LMHOSTS, make sure you identify the server as a PDC/BDC (by adding the #DOM:EMS-DOMAIN entry). It also helps to pre-load (#PRE) the PDC line at boot time.

Back to the top: Checking network connectivity. From the server, start with pinging other PCs by IP address.If it works, ping th

by nold

I think what you did with your NT Server and the other Win98 computer was right. Though, you should have done it more extensively.

Like, you should have placed the other Win98 on the place of the problem PC, if that works, then you can say that there's a problem with your Win98 PC. solution: copy the settings of that other Win98 PC on the problem PC. If this didn't work, reinstall the NIC card.

If the other Win98 doesn't work using the patch cord of your problem PC, then the patch cord might be your problem. Change the patch cord.

hope that helps.

by Member 30576776

I noted that your subnet mask should be 255.0.0.0 for the IP address that you list. That should correct your TCP/IP problems. The others' suggestions should get you going. hhp

by smurfman

I agree with answer #6, you should always start with the most simple solutions. First check the system properties and make sure that the NIC card is not conflicting with another piece of hardware. Next, open the properties for the NIC and make sure that the Check Box for Disable in this Hardware Profile is not checked and then make sure that the Exists in All Profiles is Checked. If all seems well here close out this window. Double check the network settings in the control panal, be sure that you are logging on using Client For MS Networks. Make sure that the TCPIP settings that you made were not bound to a DIAL UP ADP and not the NIC, you can see this in the Network Componants Window ( it should be the one TCP/IP -> (NIC Card Name Here). Make sure that your computer has a name, under Identification. SOME LAST RESORTS - When you are compairing the 2 Win98 Machines are they both using the same NIC card? If not you may not be compairing Apples to Apples when saying that one machine works and the othe

This discussion is closed to new replies.