I have 2 PC I've set up as an NT Server (PDC) and a NT Workstation. The server PC is dual booted with win 95 and Workstation with Win 98. The 2 PCs are networked and when booted as both 95 & 98, the network works fine. I can ping the ip addreses of each PC correctly.

However when I boot the PCs up as NT Server and NT Workstation, I am unable to see any network and can't ping the ip addresses of the other PC.
TCP/IP seems to be installed correctly on each PC as I can ping the loopback address (127.0.0.1) ok. From the Server I can also ping the Servers own ip address (setup as 100.100.100.1), but I, can't ping the address of the Workstation (ip address of 100.100.100.2).
I keeping getting a request timed out message.
The network cards installed OK in NT and are bound to the TCP/IP protocol.
Another thing I find is that after pinging, if I do an "arp -a" from the Server ip=100.100.100.1,) the ip address of the Workstation and its physical NIC address are given. So it did seem to get some limited kind of connectivity.

Any help would be greatly appreciated

Go to Start>>Run>< type in CMD, press return
Type
ipconfig/all

and tell me what you see... do the IP addresses show up there? gateway is empty?

What I get for ipconfig /all is as follows:

Windows NT IP Configuration

Host name.... Dell
DNS Server
Node type...................... Hybrid
Netbios scope id
IP routing enabled.............. No
Wins proxy enabled.............. No
NetBIOS resolution uses DNS .... No

Ethernet Adapter

Description .............. PCI Bus Master
Physical Address .... 00-80- etc
DHCP enabled ........ No
IP address .......... 100.100.100.1
subnet mask.......... 255.255.255.0
Default gateway
Primary WINs Server.. 100.100.100.1

Try setting manual ip addresses of 192.168.10.1 for the server and 192.168.10.2 for the workstation. If that fails install the DHCP service from the system option in control panel on the server and set the tcp/ip protocol to automatically assign ip address. Make sure that the scope range cover the ip addresses listed above - eg: have a scope of 192.168.10.2 to 192.168.10.3
(192.168.10.1 would be the server.) Make sure that the subnet mask is the same on both machines. eg: 255.255.255.0

Should sort it.

Pete

Sorry, Pete, that shouldn't matter at all..

Ed: Do the same for the NT Workstation and let me know what you see for ipconfig/all

On the NT workstation put 100.100.100.1 as the gateway.... let us know.

What I get for ipconfig /all for the Workstation is as follows:

Windows NT IP Configuration

Host name.... AST
DNS Server
Node type...................... Broadcast
Netbios scope id
IP routing enabled.............. No
Wins proxy enabled.............. No
NetBIOS resolution uses DNS .... No

Ethernet Adapter

Description .............. PCI Bus Master
Physical Address .... 00-80-AD etc
DHCP enabled ........ No
IP address .......... 100.100.100.2
subnet mask.......... 255.255.255.0
Default gateway ..... 100.100.100.1

Just to give more info on this problem that is really annoying me.
Maybe it's my fault and my limited practical knowledge of NT Server (so much for studying the MCPs). That's why I wanted to network the 2 PCs and increase my pratcial knowledge.

The Server and WS software are the evaluation copies, build 4.00 1381 which as far as I'm aware is Service Pack 1 (could this be the problem)?

I have the latest NT NDIS 4.0 drivers for my CNET Pro120B PCI Fast Ethnernet Adapters.

Today I re-installed the Server without any problems then the Workstation with just one problem - when I tried to make it a member of the domain (Server up and running at this stage) I get the message "The Domain Controller for the Domain could not be found" so I had to leave as a Workgroup.

Both TCP/IP (ip addresses 192.168.10.1 & 192.168.10.2, subnet 255.255.255.0) and NETBEUI were the added protocols.

There are no error messages on startup (all services start ok) or in the Event Viewer.

The services installed on my server are Computer Browser, NetBIOS Interface, RPC Config, Server & Workstation

What services should I have installed to get this working?
I mean are DNS WINS DHCP etc. required just to ping between the Server and WS. Surely I should also be able to connect using NETBEUI which is the first protocol bound to the NIC.

As I had mentioned in my original message, my dual-booted systems when booted under Win 95 and 98 have no problems seeing the network, so NIC hardware and cable are good. Does it just come down to the NT drivers then, although I have NDIS 4 drivers for NT. (the NIC are not on the HCL -- should that matter)

Thanks for all your previous suggestions and Thanks in advance if this can be solved

P.S I know I can probably pass the MCPs without doing this but I think that it sucks having paper MCPs and not being able to set up a simple 2 PC NT network.

Regards ED

Sorry , but if you have a 'CLASS A' ip address 100.100.100.1 and a 'CLASS C' subnet mask .. then its having problems for starters , dean , and yes pete was right it should matter.

Although I can't agree with the tone of Dean Suxs - There may be an issue with dual booting a PDC - as far as I'm aware mate it isn't usually done.

Id like to get to know you tech wise.
class a 1-126 subnet 255.0.0.0 hosts per network 16,777,214....
127.0.0.1 reserved
class b 128-191 subnet 255.255.0.0 HPN 5,534
class c 192-233 subnet 255.255.255.0 HPN 254
Class C addresses are used for small networks
link for further explanation
http://www.microsoft.com/windows2000/library/resources/reskit/samplechapters/cnbb/cnbb_tcp_pnmz.asp
check for same domain and or workgroup make sure both computer names are different
do you log in to your nt domain or at least try from WS?
both 10base t or 100 base t or 10/100 cards same? I think i read somewhere that hooking up directly to server there are 2 different cables cat5
you might try the other kind of cable or hook both up to a hub..
im a msce in trainning with only books but have a network up and running tcp/ip

Isnt that the wrong subnet mask

*************** Problem Solved **************

I am now able to connect/ping between the Server and Workstation.

The final solution (God I hate this) was an updated NT4.0 Driver.

I thought the driver I had was the latest one because I had gone
directly to the US home page of the manufacturer and in their Driver
Library, the latest driver (they have "NEW" beside the download)
for my CNet Pro120 (B) PCI Fast Ethernet Adapter card was the same
as the one bundled with my NIC.

I had tried everthing suggested and more -- re-installing O/S,
getting rid of dual-booted PCs and just having 1 PC with Server
on it and the other PC trying different O/Ss - hoping for a
connection -- not even a whimper.

I eventually did a search for this NIC and found another CNet site
where I downloaded drivers for a CNet Pro120 (C) PCI Fast Ethernet
adapter card. I decided to give this a go anyway and lo and behold
the readme file said that the driver would work with the A, B and C
versions.

Many Thanks for all your help and suggestions. It was fun, tearing my
hair out wondering what the problem could be, but I can honestly say I
learned a lot just fooling around with protocols, NIC drivers, numerous
O/S, pinging TCP/IP and examining Event Viewer etc.

Oh I hate those Drivers.

Regards ED