| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 28433 | 2002-12-19 07:28:00 | Windows 98SE TCP/IP home networking.....Success at last!! | Terry Porritt (14) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 107558 | 2002-12-19 07:28:00 | The aim of the exercise was to network 2 computers an AMD 900 Duron and an AMD K6 300 both running Windows 98SE, using Netbeui for file and printer sharing, and TCP/IP for ICS (Internet Connection Sharing) . Both computers to have dial up networking functionality, and the bindings to be set so that security would be maximised as per Steve Gibsons bindings recommendations . The reason for doing this was to be ready for when Telecom activate ADSL in the area . I would then have a choice of going the router way or an internal PCI modem and ICS . Sounds easy, especially when most of the reference sources say more or less the same thing, and there are lots of web sites giving step by step instructions . The network cards are 10Mbps with BNC and RJ45 sockets . I used thin ethernet coax with terminators for cheapness, the comps are about 10 metres apart . Installing the cards was straightforward, Win98 detected and loaded the necessary drivers . Netbeui was installed as per instructions and file sharing activated ok . Very easy, the comps talked to one another, and DOS test utility showed Tx/Rx between them ok, and files were able to be transfered across . So at this stage these were the adapters and protocolls installed: Client for Microsoft Networks . Dial-Up Adapter . Realtek RTL8029 NIC . Netbeui TCP/IP File and printer sharing for Microsoft Networks . Windows Logon was set as the primary network logon The bindings were as suggested by Steve Gibson, ie only netbeui bound to Client For Microsoft Networks and File sharing and Netbios not enabled over TCP/IP . Fine, now to install TCP/IP for the network cards . That was apparently easy to do also, and TCP/IP->Realtek RTL8029 NIC properties were checked according to the book with no bindings to Client or File sharing and appropriate IP addresses set like 192 . 168 . 0 . 1 and 192 . 168 . 0 . 2 and proper computer names and same workgroup etc . etc . Any surplus components that Windows decided to load univited were removed . The only problem was that the computers couldnt ping one another . Running Winipcfg only showed PPP Adapter in the drop down box, no sign of the NIC adapter . This in fact is a very useful tool to check whether TCP/IP is going to work . If there is no NIC adapter detected then no way can TCP/IP work . After lots of strife, lots of reading, lots of trial and error, this is what I learned . Win98SE can be a pain :( Also it transpires the order in which components are installed can have dramatic effects, even though 2 installations are apparently identicle in every way with identicle settings . This is the nitty-gritty as far as I can remember :) Remove all components from Network and remove the NIC, reboot, shut down . Re-fit NIC and let it be redetected, Windows will also install Client for MS networks . Install Netbeui . Install File and printer sharing . Install Dial-up adapter . Install TCP/IP Now remove anything not required and reset the bindings as per Steve Gibson and have the Obtain an IP Address in the TCP/IP->NIC properties checked . Reboot . Now this is the really clever bit thanks to Livingston and Straub . Win 98 automatically assigns each computer an IP address . Running Winipcfg now shows the NIC adapter AND the IP assigned by Windows together with the Subnet Mask . Copy these into the TCP/IP->NIC properties-IP Address tab, and check Specify an IP address . Decide which machine is going to be the gateway and add its IP address into the Gateway setting of the other machine . There was one further glitch however . Running Winipcfg on the older K6-300 machine showed only the NIC adapter, the PPP dial-up adapter no longer worked . The reverse of the original problem . After a bit more strife the answer was to install via the Network icon, another TCP/IP->Dial-Up Adapter . This worked, showed up in Winipcfg and the machine can now also dial out and make an Internet connection . Great So in summary; 2 networked computers, file sharing via Netbeui, each with dial up, and a working TCP/IP link between them . Next task: install Internet Connection Sharing, I hope that is going to be easier :) |
Terry Porritt (14) | ||
| 107559 | 2002-12-19 07:48:00 | Glad you managed to get it working Terry. Hope the next part goes to plan :) | -=JM=- (16) | ||
| 107560 | 2002-12-19 08:37:00 | Hey Getting computers to "talk" and see eachother is the hardest part (that I find) in networking.. From there anything you do is a breeze Congratulations and good luck CyberChuck |
cyberchuck (173) | ||
| 107561 | 2002-12-19 09:06:00 | i tend to find the networking gets iffy if netbios is unbound. hence i use ipx/spx with netbios support and let the firewall block the netbios over tcp/ip. ics is straight forward, just install on the gateway machine. nothing esle needs to be done. DO NOT use the disk optoin as you already have the settings done. ics config from practicallynetworked.com (need to check that addy) helps a lot. |
tweak'e (174) | ||
| 107562 | 2002-12-19 09:38:00 | add to that. i just disabled netbios over tcp/ip with no apparant ill effects. | tweak'e (174) | ||
| 1 | |||||