LAN problems

[rikytik]

Sephiroth, took a look at the thread. Bummer. At least it's a small consolation that it's "them" and not "you".

I had no idea dsl providers use MAC, since Bell Canada uses just the user/password system using a connection manager program. They permitted (at least last year) 2 different pc's to be connecected (using conection sharing).

Re NICS, My Nr. 2 PC is an MSI Ultra KT-4 (6590)and (fortunately???) didn't come with an on board NIC. But, I've had trouble in the past with a NIC that failed. I got a new one that worked. Later I assembled another pc and moved the failed NIC to it and it is still there working on my Nr. 1 pc (Asus A7V8X mobo) Go figure. This stuff is enough to drive a guy to drink sometimes. have a beer on me!

[Sephiroth]

Quote:

Originally posted by nnuxx+Jun 15 2003, 12:50 AM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (nnuxx @ Jun 15 2003, 12:50 AM)</td></tr><tr><td id='QUOTE'>to bad shephirod
cant u try to install a chipset driver for the NIC only, instead of the MSI's Mobo drivers?? might do the trick maybe it probably is a realtek or something
maybe a firmware upgrade to the modem could solve it
that is if yr willing to go for all the trouble, instead of just sticking a PCI in the freakinn thing, hehe [/b]

i tried lol, some people solved their problem by manually entering the mac address for the onboard nic in the bios that's on a sticker on the motherboard, so i pulled the board out of my case, wrote it down, tried it, flashed the bios, and used nvidia's reference drivers instead of the ones MSI have, and none of it worked, piece of ****, lol, so i put my SMC nic in and it worked perfectly fine, bastards

<!--QuoteBegin--rikytik@Jun 15 2003, 04:40 AM
Sephiroth, took a look at the thread.&nbsp; Bummer.&nbsp; At least it's a small consolation that it's "them" and not "you".&nbsp;

I had no idea dsl providers use MAC, since Bell Canada uses just the user/password system using a connection manager program.&nbsp; They permitted (at least last year) 2 different pc's to be connecected (using conection sharing).

Re NICS, My Nr. 2 PC is an MSI Ultra KT-4 (6590)and (fortunately???) didn't come with an on board NIC.&nbsp; But, I've had trouble in the past with a NIC that failed.&nbsp; I got a new one that worked.&nbsp; Later I assembled another pc and moved the failed NIC to it and it is still there working on my Nr. 1 pc (Asus A7V8X mobo)&nbsp; Go figure.&nbsp; This stuff is enough to drive a guy to drink sometimes.&nbsp; have a beer on me!&nbsp; [/quote]

i know, that's what me and DoG were talking about last night, we really both hate computers, we can fix anybody's computer except for our own, anybody can bring me their computer and give me a few hours and i'll have it stable as hell, but when it comes to my own it has more bugs than half the software MS has wrote in the past 10 years combined lolol

[Sephiroth]

Quote:

Originally posted by mikeh420@Jun 14 2003, 07:35 PM
Yep, got the Alcatel. First one died after 11 months, but got a new one under warranty and it's 2 yrs old. Also, the Linksys router takes care of DHCP, so I don't have to specify IP addr on my 2 PCs, the first one on grabs 192.168.1.100, the second gets *.*.*.101, etc. The only problem(?), if I need to configure the DSL modem (which I haven't yet), I need to connect directly from the NIC to the modem. Otherwise, it's very reliable.

though it isn't much of a better solution, there is one way i've found around that, if your router has an uplink port on it, plug the modem into your uplink port instead of the wan port, and you can access it, not much of a better solution, but at least you still have LAN access while you're configuring the modem

[Cactus]

Quote:

Originally posted by Sephiroth@Jun 14 2003, 04:51 AM
DSL Modem:

IP = 192.168.1.1
Subnet = 255.255.255.0

Router:

IP = 192.168.1.2
Subnet = 255.255.255.0

PC 1:

IP = 192.168.1.3
Subnet = 255.255.255.0

PC 2:

IP = 192.168.1.4
Subnet = 255.255.255.0

...snip...

If my router is in the middle between my modem and my machines, then I can see the modem and connect fine.

Weird...

Isn't a router used to route IP packets between different IP subnets???? That should mean your router has at least TWO ip address (or else ir won't be a router ) and the two IP addresses can NOT be in the same IP subnet range. The LAN side of your router is 192.168.1.x with mean the WAN side connecting to your router can not (I repeat can NOT) be 182.168.1.x, and neighter can the IP of your ADSL modem.

Does this makes any sense?

Haller me on MSN if you don't get it to work. Maybe, just maybe...

[rikytik]

If I got it right, what he's done is used the LAN switch in the router to connect the modem to the pc's, thus bypassing the router itself.

[Cactus]

Ah, My fault. That explains it...

[BearCat]

Quote:

Originally posted by Cactus@Jun 15 2003, 10:45 PM
... The LAN side of your router is 192.168.1.x with mean the WAN side connecting to your router can not (I repeat can NOT) be 182.168.1.x, and neighter can the IP of your ADSL modem.

Does this makes any sense?

No !
This don't make any sense.....
as 192.168.1.x and 182.168.1.x
are 2 different networks, and a router is "routing" traffic between networks :P

/Peace Cactus, I guess it was a typho