Jump to content

Connecting a Windows 98 Comp to My comp


emh
 Share

Recommended Posts

Well, I fixed the problem about eth1 not wanting to start at boot.

 

And after replacing a fan in my Linux computer, I now can just leave it on all the time again, so I don't have to restart it and worry about losing the connection to the Windows computer.

 

Or so I thought.......

 

However, just now, when my fiance tried to access the internet (I had it working before, and I hadn't restarted my Linux computer since then), she couldn't get on. I had to run the setup program in MCC before it worked on her computer.

 

What happened there? I would have thought that not having to restart the Linux computer would mean it would finally work. But I still had to re-run the setup program before my fiance could get on again.

 

Should I just break down and buy an ethernet hub or a router?

 

:\

 

Oh, and to answer a previous question, I've done it both ways, with my fiance's computer on and off, and it just doesn't stick.

Edited by emh
Link to comment
Share on other sites

what is the output of route and ifconfig -a?

linux:~ # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
linux:~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:8D:4C:4A:AD
         inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: fe80::250:8dff:fe4c:4aad/64 Scope:Link
         UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:809 errors:0 dropped:0 overruns:0 frame:0
         TX packets:724 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:939336 (917.3 Kb)  TX bytes:134621 (131.4 Kb)
         Interrupt:11 Base address:0xe800

Link to comment
Share on other sites

Currently, everything is working, (let's see how long this will last.......)

 

The output of "route":

Kernel IP routing table

Destination  Gateway      Genmask      Flags Metric Ref    Use Iface

adsl-64-219-61- *            255.255.255.255 UH    0      0        0 ppp0

192.168.1.0  *            255.255.255.0 U  0      0        0 eth1

169.254.0.0  *            255.255.0.0  U  0      0        0 eth0

127.0.0.0    *            255.0.0.0    U  0      0        0 lo

default      adsl-64-219-61- 0.0.0.0      UG    0      0        0 ppp0

 

The output of ifconfig -a :

 

eth0      Link encap:Ethernet  HWaddr 00:50:2C:04:16:12

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:62898 errors:0 dropped:0 overruns:0 frame:9

          TX packets:41678 errors:0 dropped:0 overruns:0 carrier:0

          collisions:74 txqueuelen:100

          RX bytes:63492577 (60.5 Mb)  TX bytes:5949806 (5.6 Mb)

          Interrupt:11 Base address:0xc000

 

eth0:9    Link encap:Ethernet  HWaddr 00:50:2C:04:16:12

          inet addr:169.254.18.159  Bcast:169.254.255.255  Mask:255.255.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          Interrupt:11 Base address:0xc000

 

eth1      Link encap:Ethernet  HWaddr 00:30:BD:2B:7B:57

          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:24637 errors:0 dropped:0 overruns:0 frame:0

          TX packets:45499 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:100

          RX bytes:1908345 (1.8 Mb)  TX bytes:47717715 (45.5 Mb)

          Interrupt:10 Base address:0x9000

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:110 errors:0 dropped:0 overruns:0 frame:0

          TX packets:110 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:6937 (6.7 Kb)  TX bytes:6937 (6.7 Kb)

 

ppp0      Link encap:Point-to-Point Protocol

          inet addr:64.219.60.44  P-t-P:64.219.61.254  Mask:255.255.255.255

          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1

          RX packets:41270 errors:41358 dropped:0 overruns:0 frame:0

          TX packets:22186 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:3

          RX bytes:43217554 (41.2 Mb)  TX bytes:1424827 (1.3 Mb)

Link to comment
Share on other sites

  • 4 weeks later...

I guess nobody knows how to fix the problem?

 

By the way, my fiance upgraded (using the term loosely) to Windows XP, and we still have the problem of her computer not wanting to recognize the internet connection.

 

I should state that I used a Crossover Cable to connect the two computers. Would it make a difference if I spent some extra dollars and used a regular network cable instead?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...