Re: Network problems...
racquadro@uspif1.if.usp.br wrote:
>
> I have two PCs. A 80386 and a Pentium. They have Ethernet cards (NE 2000) and Windows 3.11, on the 386, and Windows 95, on Pentium. With this system I can share files, printers...
> Months ago, I have diveded my hard disk with fdisk to install Linux and Windows 95 on the Pentium.
> Yesterday, I installed the TCP/IP protocol on the 386. I wnat to know how can I logon at Linux, from the 386.
> The situation of address on Linux is this:
>
> IP Adreess: 123.123.123.123
> Netmask: 255.255.255.0
> Network Address: 123.123.123.0
> Broadcast Address: 123.123.123.255
> Gateway Address: 123.123.123.1
> Nameserver Address: 127.0.0.1
>
> What is the configuration that I have to change on the Windows 3.11 on TCP/IP?
You really shouldn´t use 123.123.123.x addresses for your local network
if you haven´t received that address from your ISP. To be on the safe
side use the net 192.168.x.0 instead. This is a designated transfer
network that´s definitely not routed on the Internet.
A usable setup would be:
Linux: IP 192.168.42.1, Mask 255.255.255.0, Broadcast 192.168.42.0,
no DNS, no Gateway.
Win/PC: IP 192.168.42.2, mask 255.255.255.0, Broadcast 192.168.42.0,
no DNS, use LMHOSTS lookup, no Gateway.
On the Linux machine, set /etc/resolv.conf to "order host,bind", then
create a /etc/hosts file containing
127.0.0.1 localhost
192.168.42.1 linux
192.168.42.2 winpc
Copy that file to c:\<windirecotry>\lmhosts or copy the lmhosts.sam
file found there to lmhosts and edit it to use those numbers.
This is assuming that you don´t have access to te Internet. Since
all of your machines are on the same net, you really don´t need a
Gateway. You also don´t need DNS lookup since you can maintain your
hosts file pretty easily.
HTH,
--
Thomas Baetzler, thb@regioservice.de, thb@spectre.ka.sub.org
<A HREF="http://home.pages.de/~thb/">thb's Homepage</A>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: