|
|
|
Yep me again - this time a network adapter problem
|
Original Message
|
Name: Kevin D
Date: October 6, 1999 at 20:15:17 Pacific
Subject: Yep me again - this time a network adapter problem
|
Comment: We have recently moved from WIN98 and installed NT. We intend to operate a peer to peer network (not ideal, but the budget is tight!). Everything has gone reasonably well with the administration machine (other than the dat drive!), the network adapter is up and running and picking up our geriatric 486 using TPC/IP protocol (IP 10.1.10.1 Subnet 255.255.255.0). However, despite following exactly the same proceedure as before (other than new IP addresses - 10.1.10.2 & 10.1.10.3) the two other NT machines will not detect the Realtek RTC 8029 PCI adapters. At start up we get an error message that at least one device driver has failed. Pinging the two machines confirms that they are not communicating. I have tried movinfg the adapter car to another slot but no use. I have swapped the adapters that are not running with that which is and on they run perfectly? What is going on - can anyone help? Thanks to all (even if you have simply read this problem!) - Kev.
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: graeme
Date: October 7, 1999 at 00:29:55 Pacific
|
Reply: (edit)OK you mentioned these adapter cards have been used before in 9x pcs...get yourself the setup disk to these NICs and run the configuration setup....Then you can note exactly what these cards have been set to. Note IRQ and Hex address. NT has very limited plug and pray because of the HAL, and does not always detect cards correctly. Install the card, and it's drivers, then manually check to see and set the resources of the card. Also in the setup check that the card is using the right interface eg BNC or TP etc hope this helped a little'
Cheers
 Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: James Gelb
Date: October 10, 1999 at 15:15:31 Pacific
|
Reply: (edit)I;m not sure if this is your problem, but. . . 255.255.255.0 is a class C subnet mask; however, 10.1.10.x is a class B address. Try changing your ip addresses so that the most significant byte is 192. That way your address will be in the Class C range and correspond to your subnet mask.
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: James Gelb
Date: October 10, 1999 at 15:16:42 Pacific
|
Reply: (edit)I;m not sure if this is your problem, but. . . 255.255.255.0 is a class C subnet mask; however, 10.1.10.x is a class A address. Try changing your ip addresses so that the most significant byte is 192. That way your address will both be in the Class C range and correspond to your subnet mask.
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: russ
Date: October 10, 1999 at 20:05:16 Pacific
|
Reply: (edit)You may need to install netbeui ,, i had the same problem till i installed netbeui i couldnt get the pc's to see each other
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
|
|
|
