Q I have developed a small Windows 95 network which uses TCP/IP. The network works fine, but when trying to access it from my home PC, I cannot communicate with my work PC. I have installed TCP/IP at home and the network configuration is correct. Do I have to set up one (or both) computers as a server to allow the incoming call to proceed? If so, how do I do this?
- Steven Woolston
A You need to set up one of the computers on your LAN as a dial-up server. This is not built into Windows 95 -- you need to install the Microsoft Plus! pack. The ability to dial in to this server is built-into Windows 95.
The way that Windows 95 Dial-Up Networking normally works is that the two modem-equipped computers talk to each other using a protocol called NetBEUI. This should be loaded onto both computers irrespective of what networking protocol you are using on your LAN. The dial-up server acts as a gateway and converts packets of data into a format that your LAN can understand. Now for the big problem. Windows 95 can act as a gateway to NetBEUI and IPX/SPX networks, but not for a TCP/IP network. This means that you will only be able to access network resources on the computer that you are dialling into.
Your options are either to move your network over to IPX/SPX or NetBEUI. NetBEUI is the simplest protocol for small networks, and I recommend it for this reason.
TCP/IP networking is very good for large networks, which is why it has been used for the Internet -- a network that spans the world. Its complexity makes it less viable for small networks. If you are serious about using TCP/IP on your network, you should consider using Windows NT server or Linux on your main server. Not only will you be able to dial in using TCP/IP but these operating systems have other built-in features that are useful for running a TCP/IP network.
- Roy Chambers
|
Category: Networking, Communications
Issue: Feb 1998
Pages: 156-158
|