alt.certification.network-plus - Linksys router and CAT5 cable?

Author

Linksys router and CAT5 cable?

JonnieStyle

2002-09-28, 11:29 am

To recap:

A guy I know bought a Linksys router (4-port...not wireless) and brought it
home to connect two pc's to the internet (shaw high speed).
He previously had two NIC's in one computer and was using NAT software to
share, therefore his *other* machine was connected using a crossover
cable...

He removed the second NIC, and plugged in one machine. No problem. He
plugged the other machine into the "uplink" port on the router (and the link
lights came on), but he's unable to release and renew his IP address nor
connect to the internet (duh.). (He's getting a 169.254.....)

Though the crossover cable worked fine before, I suggested we make a
straight through cable and try a regular port (...'cause what else is there
to try?!)

I sliced off the ends of the crossover cable, and crimped on some straight
thru ends.

Still doesn't work.

I tested the cable with an ohmeter, an (as I write this post) am connected
to the internet with that very cable (it's about 30 ft)

So what's the deal? Is this an inherent problem with Linksys routers? I've
got a D-LINK switch, and there doesn't seem to be a problem. Is there too
much capacitance in the cable and Linksys doesn't use inductors to counter
the signal?

I don't know...!

So I brought this cable to work and tried it on two more Linksys router with
the same problem.
Link lights are on where they should be on, machine is set to DHCP, no IP
address coming down the cable to the NIC - keep getting 169.254 blah blah...

Has anybody got the foggiest idea why this cable works on *some* equipment
and not others?

(BTW - "let the link light be your guide" doesn't cover this problem... The
link lights are responding the way it should...!)

--
JonnieStyle
jonniestyle@hotmail.com

Wyrm@home.com

2002-09-28, 1:28 pm

I had a very similar problem, kept getting 169.164........... which
was a self supplied IP by the card.
Go into the Linksys configuration and under the DHCP tab check how
many DHCP users it is configured for.

Wyrm

On Sat, 28 Sep 2002 15:14:13 GMT, "JonnieStyle"
<jonniestyle@hotmail.com> wrote:

>To recap:
>
>A guy I know bought a Linksys router (4-port...not wireless) and
brought it
>home to connect two pc's to the internet (shaw high speed).
>He previously had two NIC's in one computer and was using NAT
software to
>share, therefore his *other* machine was connected using a crossover
>cable...
>
>He removed the second NIC, and plugged in one machine. No problem.
He
>plugged the other machine into the "uplink" port on the router (and
the link
>lights came on), but he's unable to release and renew his IP address
nor
>connect to the internet (duh.). (He's getting a 169.254.....)
>
>Though the crossover cable worked fine before, I suggested we make a
>straight through cable and try a regular port (...'cause what else is
there
>to try?!)
>
>I sliced off the ends of the crossover cable, and crimped on some
straight
>thru ends.
>
>Still doesn't work.
>
>I tested the cable with an ohmeter, an (as I write this post) am
connected
>to the internet with that very cable (it's about 30 ft)
>
>So what's the deal? Is this an inherent problem with Linksys
routers? I've
>got a D-LINK switch, and there doesn't seem to be a problem. Is
there too
>much capacitance in the cable and Linksys doesn't use inductors to
counter
>the signal?
>
>I don't know...!
>
>So I brought this cable to work and tried it on two more Linksys
router with
>the same problem.
>Link lights are on where they should be on, machine is set to DHCP,
no IP
>address coming down the cable to the NIC - keep getting 169.254 blah
blah...
>
>Has anybody got the foggiest idea why this cable works on *some*
equipment
>and not others?
>
>(BTW - "let the link light be your guide" doesn't cover this
problem... The
>link lights are responding the way it should...!)

Wyrm@home.com

2002-09-28, 2:28 pm

Nick Ramsay

2002-09-28, 4:28 pm

JonnieStyle wrote:
>
> So I brought this cable to work and tried it on two more Linksys router with
> the same problem.
> Link lights are on where they should be on, machine is set to DHCP, no IP
> address coming down the cable to the NIC - keep getting 169.254 blah blah...
>
> Has anybody got the foggiest idea why this cable works on *some* equipment
> and not others?
>
> (BTW - "let the link light be your guide" doesn't cover this problem... The
> link lights are responding the way it should...!)

I've seen this before (on Netgear, in my case). Forget the cable,
that's not the problem. It's the negotiate of the speed that's the
problem. Can you dumb down the NIC to 10mb? That sorted it out for me.

Nick Ramsay

2002-09-28, 5:29 pm

PC Trouble Shooter -->

2002-09-29, 8:28 am

Sounds like you need to clone the MAC address from the original NIC and put
it in the router. Reset cable modem & router all should work afterwards.
The cable company binds to the MAc on the NIC when they set 'em up!

Mark

"JonnieStyle" <jonniestyle@hotmail.com> wrote in message
news:9Hjl9.12075$bj5.611880@news2.telusplanet.net...
> To recap:
>
> A guy I know bought a Linksys router (4-port...not wireless) and brought
it
> home to connect two pc's to the internet (shaw high speed).
> He previously had two NIC's in one computer and was using NAT software to
> share, therefore his *other* machine was connected using a crossover
> cable...
>
> He removed the second NIC, and plugged in one machine. No problem. He
> plugged the other machine into the "uplink" port on the router (and the
link
> lights came on), but he's unable to release and renew his IP address nor
> connect to the internet (duh.). (He's getting a 169.254.....)
>
> Though the crossover cable worked fine before, I suggested we make a
> straight through cable and try a regular port (...'cause what else is
there
> to try?!)
>
> I sliced off the ends of the crossover cable, and crimped on some straight
> thru ends.
>
> Still doesn't work.
>
> I tested the cable with an ohmeter, an (as I write this post) am connected
> to the internet with that very cable (it's about 30 ft)
>
> So what's the deal? Is this an inherent problem with Linksys routers?
I've
> got a D-LINK switch, and there doesn't seem to be a problem. Is there too
> much capacitance in the cable and Linksys doesn't use inductors to counter
> the signal?
>
> I don't know...!
>
> So I brought this cable to work and tried it on two more Linksys router
with
> the same problem.
> Link lights are on where they should be on, machine is set to DHCP, no IP
> address coming down the cable to the NIC - keep getting 169.254 blah
blah...
>
> Has anybody got the foggiest idea why this cable works on *some* equipment
> and not others?
>
> (BTW - "let the link light be your guide" doesn't cover this problem...
The
> link lights are responding the way it should...!)
>
> --
> JonnieStyle
> jonniestyle@hotmail.com
>
>

PC Trouble Shooter -->

2002-09-29, 9:29 am

JonnieStyle

2002-09-29, 9:29 am

Sadly, the router is supposed to be 10/100 Mbps.

Linksys support got back to me and gave me a basic lesson in what ethernet
is. I guess they didn't actually read the problem I'm having...

I'll try the 10 Mbps trick, but I'm thinking the solution is to throw out
the Linksys and try a differnet brand.

"Nick Ramsay" <news@nospam.demon.co.uk> wrote in message
news:an58m0$kd9$1$8300dec7@new
s.demon.co.uk...
> JonnieStyle wrote:
> >
> > So I brought this cable to work and tried it on two more Linksys router
with
> > the same problem.
> > Link lights are on where they should be on, machine is set to DHCP, no
IP
> > address coming down the cable to the NIC - keep getting 169.254 blah
blah...
> >
> > Has anybody got the foggiest idea why this cable works on *some*
equipment
> > and not others?
> >
> > (BTW - "let the link light be your guide" doesn't cover this problem...
The
> > link lights are responding the way it should...!)
>
> I've seen this before (on Netgear, in my case). Forget the cable,
> that's not the problem. It's the negotiate of the speed that's the
> problem. Can you dumb down the NIC to 10mb? That sorted it out for me.
>

JonnieStyle

2002-09-29, 9:29 am

I can't get into the router's setup though.

That's the real problem. Opening a browser to http://192.168.1.1 opens a
DNS error, and not the router's configuration.
The problem is the lights indicate there is a connection, but the computer
and NIC aren't connecting.

(...and I've tried different computers and different Linksys routers - the
cable, however, works fine on other hardware...)

Figure that one out!

Cheers.

"PC Trouble Shooter -->" <mkloch@pc-troubleshooter.com> wrote in message
news:Q1Dl9.3$xU3.7949@news.abs.net...
> Sounds like you need to clone the MAC address from the original NIC and
put
> it in the router. Reset cable modem & router all should work afterwards.
> The cable company binds to the MAc on the NIC when they set 'em up!
>
> Mark
>
> "JonnieStyle" <jonniestyle@hotmail.com> wrote in message
> news:9Hjl9.12075$bj5.611880@news2.telusplanet.net...
> > To recap:
> >
> > A guy I know bought a Linksys router (4-port...not wireless) and brought
> it
> > home to connect two pc's to the internet (shaw high speed).
> > He previously had two NIC's in one computer and was using NAT software
to
> > share, therefore his *other* machine was connected using a crossover
> > cable...
> >
> > He removed the second NIC, and plugged in one machine. No problem. He
> > plugged the other machine into the "uplink" port on the router (and the
> link
> > lights came on), but he's unable to release and renew his IP address nor
> > connect to the internet (duh.). (He's getting a 169.254.....)
> >
> > Though the crossover cable worked fine before, I suggested we make a
> > straight through cable and try a regular port (...'cause what else is
> there
> > to try?!)
> >
> > I sliced off the ends of the crossover cable, and crimped on some
straight
> > thru ends.
> >
> > Still doesn't work.
> >
> > I tested the cable with an ohmeter, an (as I write this post) am
connected
> > to the internet with that very cable (it's about 30 ft)
> >
> > So what's the deal? Is this an inherent problem with Linksys routers?
> I've
> > got a D-LINK switch, and there doesn't seem to be a problem. Is there
too
> > much capacitance in the cable and Linksys doesn't use inductors to
counter
> > the signal?
> >
> > I don't know...!
> >
> > So I brought this cable to work and tried it on two more Linksys router
> with
> > the same problem.
> > Link lights are on where they should be on, machine is set to DHCP, no
IP
> > address coming down the cable to the NIC - keep getting 169.254 blah
> blah...
> >
> > Has anybody got the foggiest idea why this cable works on *some*
equipment
> > and not others?
> >
> > (BTW - "let the link light be your guide" doesn't cover this problem...
> The
> > link lights are responding the way it should...!)
> >
> > --
> > JonnieStyle
> > jonniestyle@hotmail.com
> >
> >
>
>

JonnieStyle

2002-09-29, 10:29 am

JonnieStyle

2002-09-29, 10:29 am

Barry Watzman

2002-09-29, 9:29 pm

No idea what's going on, but there's not a specific problem with the
linksys products (which I use).

The cable could be bad. Testing with any DC device does not prove that
the cable is good (although it can prove that the cable is bad). As an
example, if two wires (single wires, not a pair) are both swapped at
both ends, the cable will test good -- and will BE good -- for DC, but
won't work.

I'd try another (known good) cable. But I suspect something other than
the cable, I suspect some configuration problem, although I can't say
what it is.

[PS - sometimes when you change network configurations, entire software
protocols get removed in the process. Check that you have everything
that you need, protocol wise. The fact that it was there doesn't mean
that it still is. I once spend 3 days because Netbeui was not
installed. It had been installed, and I didn't remove it, but it "went
away" in the process of changing seemingly unrelated other items]

JonnieStyle wrote:
> To recap:
>
> A guy I know bought a Linksys router (4-port...not wireless) and brought it
> home to connect two pc's to the internet (shaw high speed).
> He previously had two NIC's in one computer and was using NAT software to
> share, therefore his *other* machine was connected using a crossover
> cable...
>
> He removed the second NIC, and plugged in one machine. No problem. He
> plugged the other machine into the "uplink" port on the router (and the link
> lights came on), but he's unable to release and renew his IP address nor
> connect to the internet (duh.). (He's getting a 169.254.....)
>
> Though the crossover cable worked fine before, I suggested we make a
> straight through cable and try a regular port (...'cause what else is there
> to try?!)
>
> I sliced off the ends of the crossover cable, and crimped on some straight
> thru ends.
>
> Still doesn't work.
>
> I tested the cable with an ohmeter, an (as I write this post) am connected
> to the internet with that very cable (it's about 30 ft)
>
> So what's the deal? Is this an inherent problem with Linksys routers? I've
> got a D-LINK switch, and there doesn't seem to be a problem. Is there too
> much capacitance in the cable and Linksys doesn't use inductors to counter
> the signal?
>
> I don't know...!
>
> So I brought this cable to work and tried it on two more Linksys router with
> the same problem.
> Link lights are on where they should be on, machine is set to DHCP, no IP
> address coming down the cable to the NIC - keep getting 169.254 blah blah...
>
> Has anybody got the foggiest idea why this cable works on *some* equipment
> and not others?
>
> (BTW - "let the link light be your guide" doesn't cover this problem... The
> link lights are responding the way it should...!)
>
> --
> JonnieStyle
> jonniestyle@hotmail.com
>
>

Barry Watzman

2002-09-29, 9:29 pm

You are getting a lot of bum advice here, and are being sent off on
"wild goose chases". I don't know what the problem is, but some of the
suggestions being made are "off the wall".

IF it works at 10 but not at 100, and if you have a good 10/100 NIC card
in the PC, then you have a cable problem. The router IS 10/100, and
while the WAN port (cable or DSL) is limited to 10, the LAN side should
work at 100 Mbps.

JonnieStyle wrote:
> Sadly, the router is supposed to be 10/100 Mbps.
>
> Linksys support got back to me and gave me a basic lesson in what ethernet
> is. I guess they didn't actually read the problem I'm having...
>
> I'll try the 10 Mbps trick, but I'm thinking the solution is to throw out
> the Linksys and try a differnet brand.
>
> "Nick Ramsay" <news@nospam.demon.co.uk> wrote in message
> news:an58m0$kd9$1$8300dec7@new
s.demon.co.uk...
>
>>JonnieStyle wrote:
>>
>>>So I brought this cable to work and tried it on two more Linksys router
>>
> with
>
>>>the same problem.
>>>Link lights are on where they should be on, machine is set to DHCP, no
>>
> IP
>
>>>address coming down the cable to the NIC - keep getting 169.254 blah
>>
> blah...
>
>>>Has anybody got the foggiest idea why this cable works on *some*
>>
> equipment
>
>>>and not others?
>>>
>>>(BTW - "let the link light be your guide" doesn't cover this problem...
>>
> The
>
>>>link lights are responding the way it should...!)
>>
>>I've seen this before (on Netgear, in my case). Forget the cable,
>>that's not the problem. It's the negotiate of the speed that's the
>>problem. Can you dumb down the NIC to 10mb? That sorted it out for me.
>>
>
>
>

Barry Watzman

2002-09-29, 10:29 pm

Barry Watzman

2002-09-29, 10:29 pm

JonnieStyle

2002-09-30, 4:29 pm

Ok get this:

The cable doesn't work with a Linksys router. But it works with a D-Link
switch, and - I suspect other devices also.
So I made a new cable in the same fashion, took another old cable I made,
and found a six foot premade cable and tried 'em all.

The three other cables connect to the router.
The original does not.

So therefore the cable is bad. But not *too* bad, because it'll work with
other devices...

Crazy, huh?

"Barry Watzman" <Watzman@neo.rr.com> wrote in message
news:3D97B620.8030803@neo.rr.com...
> No idea what's going on, but there's not a specific problem with the
> linksys products (which I use).
>
> The cable could be bad. Testing with any DC device does not prove that
> the cable is good (although it can prove that the cable is bad). As an
> example, if two wires (single wires, not a pair) are both swapped at
> both ends, the cable will test good -- and will BE good -- for DC, but
> won't work.
>
> I'd try another (known good) cable. But I suspect something other than
> the cable, I suspect some configuration problem, although I can't say
> what it is.
>
> [PS - sometimes when you change network configurations, entire software
> protocols get removed in the process. Check that you have everything
> that you need, protocol wise. The fact that it was there doesn't mean
> that it still is. I once spend 3 days because Netbeui was not
> installed. It had been installed, and I didn't remove it, but it "went
> away" in the process of changing seemingly unrelated other items]
>
>
> JonnieStyle wrote:
> > To recap:
> >
> > A guy I know bought a Linksys router (4-port...not wireless) and brought
it
> > home to connect two pc's to the internet (shaw high speed).
> > He previously had two NIC's in one computer and was using NAT software
to
> > share, therefore his *other* machine was connected using a crossover
> > cable...
> >
> > He removed the second NIC, and plugged in one machine. No problem. He
> > plugged the other machine into the "uplink" port on the router (and the
link
> > lights came on), but he's unable to release and renew his IP address nor
> > connect to the internet (duh.). (He's getting a 169.254.....)
> >
> > Though the crossover cable worked fine before, I suggested we make a
> > straight through cable and try a regular port (...'cause what else is
there

> > to try?!)
> >
> > I sliced off the ends of the crossover cable, and crimped on some
straight
> > thru ends.
> >
> > Still doesn't work.
> >
> > I tested the cable with an ohmeter, an (as I write this post) am
connected
> > to the internet with that very cable (it's about 30 ft)
> >
> > So what's the deal? Is this an inherent problem with Linksys routers?
I've
> > got a D-LINK switch, and there doesn't seem to be a problem. Is there
too
> > much capacitance in the cable and Linksys doesn't use inductors to
counter
> > the signal?
> >
> > I don't know...!
> >
> > So I brought this cable to work and tried it on two more Linksys router
with
> > the same problem.
> > Link lights are on where they should be on, machine is set to DHCP, no
IP
> > address coming down the cable to the NIC - keep getting 169.254 blah
blah...
> >
> > Has anybody got the foggiest idea why this cable works on *some*
equipment
> > and not others?
> >
> > (BTW - "let the link light be your guide" doesn't cover this problem...
The
> > link lights are responding the way it should...!)
> >
> > --
> > JonnieStyle
> > jonniestyle@hotmail.com
> >
> >
>

JonnieStyle

2002-09-30, 4:29 pm

I tried "dumbing" down the NIC to 10 - but the same symptoms crept up:

Link lights on both NIC and router, but no communication.

But the other cables I tried worked nicley.

So bad cable, right? But the cable works elsewhere. So bad cable in
relation to router.

That's gotta be it...

"Barry Watzman" <Watzman@neo.rr.com> wrote in message
news:3D97B705.1010907@neo.rr.com...
> You are getting a lot of bum advice here, and are being sent off on
> "wild goose chases". I don't know what the problem is, but some of the
> suggestions being made are "off the wall".
>
> IF it works at 10 but not at 100, and if you have a good 10/100 NIC card
> in the PC, then you have a cable problem. The router IS 10/100, and
> while the WAN port (cable or DSL) is limited to 10, the LAN side should
> work at 100 Mbps.
>
>
>
> JonnieStyle wrote:
> > Sadly, the router is supposed to be 10/100 Mbps.
> >
> > Linksys support got back to me and gave me a basic lesson in what
ethernet
> > is. I guess they didn't actually read the problem I'm having...
> >
> > I'll try the 10 Mbps trick, but I'm thinking the solution is to throw
out
> > the Linksys and try a differnet brand.
> >
> > "Nick Ramsay" <news@nospam.demon.co.uk> wrote in message
> > news:an58m0$kd9$1$8300dec7@new
s.demon.co.uk...
> >
> >>JonnieStyle wrote:
> >>
> >>>So I brought this cable to work and tried it on two more Linksys router
> >>
> > with
> >
> >>>the same problem.
> >>>Link lights are on where they should be on, machine is set to DHCP, no
> >>
> > IP
> >
> >>>address coming down the cable to the NIC - keep getting 169.254 blah
> >>
> > blah...
> >
> >>>Has anybody got the foggiest idea why this cable works on *some*
> >>
> > equipment
> >
> >>>and not others?
> >>>
> >>>(BTW - "let the link light be your guide" doesn't cover this problem...
> >>
> > The
> >
> >>>link lights are responding the way it should...!)
> >>
> >>I've seen this before (on Netgear, in my case). Forget the cable,
> >>that's not the problem. It's the negotiate of the speed that's the
> >>problem. Can you dumb down the NIC to 10mb? That sorted it out for me.
> >>
> >
> >
> >
>

JonnieStyle

2002-09-30, 5:28 pm

JonnieStyle

2002-09-30, 5:28 pm

cjt

2002-10-01, 2:28 am

JonnieStyle wrote:
>
> Ok get this:
>
> The cable doesn't work with a Linksys router. But it works with a D-Link
> switch, and - I suspect other devices also.
> So I made a new cable in the same fashion, took another old cable I made,
> and found a six foot premade cable and tried 'em all.
>
> The three other cables connect to the router.
> The original does not.
>
> So therefore the cable is bad. But not *too* bad, because it'll work with
> other devices...
>
> Crazy, huh?

Not really, although if it's truly Cat5 and made correctly (i.e. with the
right colors in the right spots of the RJ45, and not too much untwisted at
the ends) I wouldn't expect a problem. I've seen equipment that was fussy
about cables, and cables that weren't properly made.

>
> "Barry Watzman" <Watzman@neo.rr.com> wrote in message
> news:3D97B620.8030803@neo.rr.com...
> > No idea what's going on, but there's not a specific problem with the
> > linksys products (which I use).
> >
> > The cable could be bad. Testing with any DC device does not prove that
> > the cable is good (although it can prove that the cable is bad). As an
> > example, if two wires (single wires, not a pair) are both swapped at
> > both ends, the cable will test good -- and will BE good -- for DC, but
> > won't work.
> >
> > I'd try another (known good) cable. But I suspect something other than
> > the cable, I suspect some configuration problem, although I can't say
> > what it is.
> >
> > [PS - sometimes when you change network configurations, entire software
> > protocols get removed in the process. Check that you have everything
> > that you need, protocol wise. The fact that it was there doesn't mean
> > that it still is. I once spend 3 days because Netbeui was not
> > installed. It had been installed, and I didn't remove it, but it "went
> > away" in the process of changing seemingly unrelated other items]
> >
> >
> > JonnieStyle wrote:
> > > To recap:
> > >
> > > A guy I know bought a Linksys router (4-port...not wireless) and brought
> it

> > > home to connect two pc's to the internet (shaw high speed).
> > > He previously had two NIC's in one computer and was using NAT software
> to

> > > share, therefore his *other* machine was connected using a crossover
> > > cable...
> > >
> > > He removed the second NIC, and plugged in one machine. No problem. He
> > > plugged the other machine into the "uplink" port on the router (and the
> link
> > > lights came on), but he's unable to release and renew his IP address nor
> > > connect to the internet (duh.). (He's getting a 169.254.....)
> > >
> > > Though the crossover cable worked fine before, I suggested we make a
> > > straight through cable and try a regular port (...'cause what else is
> there
> > > to try?!)
> > >
> > > I sliced off the ends of the crossover cable, and crimped on some
> straight
> > > thru ends.
> > >
> > > Still doesn't work.
> > >
> > > I tested the cable with an ohmeter, an (as I write this post) am
> connected
> > > to the internet with that very cable (it's about 30 ft)
> > >
> > > So what's the deal? Is this an inherent problem with Linksys routers?
> I've
> > > got a D-LINK switch, and there doesn't seem to be a problem. Is there
> too
> > > much capacitance in the cable and Linksys doesn't use inductors to
> counter
> > > the signal?
> > >
> > > I don't know...!
> > >
> > > So I brought this cable to work and tried it on two more Linksys router
> with
> > > the same problem.
> > > Link lights are on where they should be on, machine is set to DHCP, no
> IP

> > > address coming down the cable to the NIC - keep getting 169.254 blah
> blah...
> > >
> > > Has anybody got the foggiest idea why this cable works on *some*
> equipment
> > > and not others?
> > >
> > > (BTW - "let the link light be your guide" doesn't cover this problem...
> The
> > > link lights are responding the way it should...!)
> > >
> > > --
> > > JonnieStyle
> > > jonniestyle@hotmail.com
> > >
> > >
> >

cjt

2002-10-01, 3:28 am

Barry Watzman

2002-10-01, 1:29 pm

Cables come in different qualities and can have a large number of
different kinds of defects. Do you know what the real difference is
between the different "categories" of cables ? It's primarily in the
number of twists per inch. And that number is different for each color
code pair within the same cable (e.g. the orange/orange-white pair has a
different number of twists per inch than the green/green-white pair).
Also, things like simply "crushing" the cable (but without actually
breaking or shorting anything), or putting a "kink" in it can turn a
cable from good to bad. At 100 Mbps, the cable has "transmission line
properties" that, to most of us, are almost "black magic" in nature.

So, yes, you have a cable that is marginal on that particular router.
I'll tell you that if it's marginal on the Linksys, it's marginal on the
D-Link as well. It's just that on the Linksys, it falls on the "don't
work" side of "marginal", while on the D-Link, it's on the "work" side.
But still marginal, for a reason that no one may ever find out.

JonnieStyle wrote:
> Ok get this:
>
> The cable doesn't work with a Linksys router. But it works with a D-Link
> switch, and - I suspect other devices also.
> So I made a new cable in the same fashion, took another old cable I made,
> and found a six foot premade cable and tried 'em all.
>
> The three other cables connect to the router.
> The original does not.
>
> So therefore the cable is bad. But not *too* bad, because it'll work with
> other devices...
>
> Crazy, huh?
>
> "Barry Watzman" <Watzman@neo.rr.com> wrote in message
> news:3D97B620.8030803@neo.rr.com...
>
>>No idea what's going on, but there's not a specific problem with the
>>linksys products (which I use).
>>
>>The cable could be bad. Testing with any DC device does not prove that
>>the cable is good (although it can prove that the cable is bad). As an
>>example, if two wires (single wires, not a pair) are both swapped at
>>both ends, the cable will test good -- and will BE good -- for DC, but
>>won't work.
>>
>>I'd try another (known good) cable. But I suspect something other than
>>the cable, I suspect some configuration problem, although I can't say
>>what it is.
>>
>>[PS - sometimes when you change network configurations, entire software
>>protocols get removed in the process. Check that you have everything
>>that you need, protocol wise. The fact that it was there doesn't mean
>>that it still is. I once spend 3 days because Netbeui was not
>>installed. It had been installed, and I didn't remove it, but it "went
>>away" in the process of changing seemingly unrelated other items]
>>
>>
>>JonnieStyle wrote:
>>
>>>To recap:
>>>
>>>A guy I know bought a Linksys router (4-port...not wireless) and brought
>>
> it
>
>>>home to connect two pc's to the internet (shaw high speed).
>>>He previously had two NIC's in one computer and was using NAT software
>>
> to
>
>>>share, therefore his *other* machine was connected using a crossover
>>>cable...
>>>
>>>He removed the second NIC, and plugged in one machine. No problem. He
>>>plugged the other machine into the "uplink" port on the router (and the
>>
> link
>
>>>lights came on), but he's unable to release and renew his IP address nor
>>>connect to the internet (duh.). (He's getting a 169.254.....)
>>>
>>>Though the crossover cable worked fine before, I suggested we make a
>>>straight through cable and try a regular port (...'cause what else is
>>
> there
>
>>>to try?!)
>>>
>>>I sliced off the ends of the crossover cable, and crimped on some
>>
> straight
>
>>>thru ends.
>>>
>>>Still doesn't work.
>>>
>>>I tested the cable with an ohmeter, an (as I write this post) am
>>
> connected
>
>>>to the internet with that very cable (it's about 30 ft)
>>>
>>>So what's the deal? Is this an inherent problem with Linksys routers?
>>
> I've
>
>>>got a D-LINK switch, and there doesn't seem to be a problem. Is there
>>
> too
>
>>>much capacitance in the cable and Linksys doesn't use inductors to
>>
> counter
>
>>>the signal?
>>>
>>>I don't know...!
>>>
>>>So I brought this cable to work and tried it on two more Linksys router
>>
> with
>
>>>the same problem.
>>>Link lights are on where they should be on, machine is set to DHCP, no
>>
> IP
>
>>>address coming down the cable to the NIC - keep getting 169.254 blah
>>
> blah...
>
>>>Has anybody got the foggiest idea why this cable works on *some*
>>
> equipment
>
>>>and not others?
>>>
>>>(BTW - "let the link light be your guide" doesn't cover this problem...
>>
> The
>
>>>link lights are responding the way it should...!)
>>>
>>>--
>>>JonnieStyle
>>>jonniestyle@hotmail.com
>>>
>>>
>>
>
>

Barry Watzman

2002-10-01, 2:29 pm

>Pearl Jam

2002-10-05, 3:25 pm

Nothing wrong with the MAC, NIC or CABLE(s)...

The IP you are getting is the generic default IP that Windows throws
at it when there has been as sudden change in the configuration and is
unable to "reprogramm" the original IP in the network settings...

Anyway... the way i been able to get rid of this problem has been to
boot the machine into the C: prompt and run SCANREG /RESTORE then i
select the latest known good last time it booted with network setting
and all... and the NIC goes back to working just fine... is happened
twice already... and both times has worked.

However, i was told that by removing the NIC and letting Win boot to
reconfigure itself without any networking config... it should blow the
error too... but i never got try that one.

Good luck M8!

On Sun, 29 Sep 2002 09:15:04 -0400, "PC Trouble Shooter -->"
<mkloch@pc-troubleshooter.com> wrote:

>Sounds like you need to clone the MAC address from the original NIC and put
>it in the router. Reset cable modem & router all should work afterwards.
>The cable company binds to the MAc on the NIC when they set 'em up!
>
>Mark
>
>"JonnieStyle" <jonniestyle@hotmail.com> wrote in message
>news:9Hjl9.12075$bj5.611880@news2.telusplanet.net...
>> To recap:
>>
>> A guy I know bought a Linksys router (4-port...not wireless) and brought
>it
>> home to connect two pc's to the internet (shaw high speed).
>> He previously had two NIC's in one computer and was using NAT software to
>> share, therefore his *other* machine was connected using a crossover
>> cable...
>>
>> He removed the second NIC, and plugged in one machine. No problem. He
>> plugged the other machine into the "uplink" port on the router (and the
>link
>> lights came on), but he's unable to release and renew his IP address nor
>> connect to the internet (duh.). (He's getting a 169.254.....)
>>
>> Though the crossover cable worked fine before, I suggested we make a
>> straight through cable and try a regular port (...'cause what else is
>there
>> to try?!)
>>
>> I sliced off the ends of the crossover cable, and crimped on some straight
>> thru ends.
>>
>> Still doesn't work.
>>
>> I tested the cable with an ohmeter, an (as I write this post) am connected
>> to the internet with that very cable (it's about 30 ft)
>>
>> So what's the deal? Is this an inherent problem with Linksys routers?
>I've
>> got a D-LINK switch, and there doesn't seem to be a problem. Is there too
>> much capacitance in the cable and Linksys doesn't use inductors to counter
>> the signal?
>>
>> I don't know...!
>>
>> So I brought this cable to work and tried it on two more Linksys router
>with
>> the same problem.
>> Link lights are on where they should be on, machine is set to DHCP, no IP
>> address coming down the cable to the NIC - keep getting 169.254 blah
>blah...
>>
>> Has anybody got the foggiest idea why this cable works on *some* equipment
>> and not others?
>>
>> (BTW - "let the link light be your guide" doesn't cover this problem...
>The
>> link lights are responding the way it should...!)
>>
>> --
>> JonnieStyle
>> jonniestyle@hotmail.com
>>
>>
>

>Pearl Jam

2002-10-05, 10:23 pm

Like I said... once a system goes bonkers and gives that kinda generic
IP address... no matter what you do... you will NOT access the net or
anything on the LAN or WAN... not even printers being shared...

And like I said before... boot the pc to a C: prompt and run SCANREG
/RESTORE ...then u select by date the best file u want to go back to
and it will release that stupid IP... hence allowing you to
reconfigure it.

>PJ<

On Sun, 29 Sep 2002 14:51:25 GMT, "JonnieStyle"
<jonniestyle@hotmail.com> wrote:

>I can't get into the router's setup though.
>
>That's the real problem. Opening a browser to http://192.168.1.1 opens a
>DNS error, and not the router's configuration.
>The problem is the lights indicate there is a connection, but the computer
>and NIC aren't connecting.
>
>(...and I've tried different computers and different Linksys routers - the
>cable, however, works fine on other hardware...)
>
>Figure that one out!
>
>Cheers.
>
>"PC Trouble Shooter -->" <mkloch@pc-troubleshooter.com> wrote in message
>news:Q1Dl9.3$xU3.7949@news.abs.net...
>> Sounds like you need to clone the MAC address from the original NIC and
>put
>> it in the router. Reset cable modem & router all should work afterwards.
>> The cable company binds to the MAc on the NIC when they set 'em up!
>>
>> Mark
>>
>> "JonnieStyle" <jonniestyle@hotmail.com> wrote in message
>> news:9Hjl9.12075$bj5.611880@news2.telusplanet.net...
>> > To recap:
>> >
>> > A guy I know bought a Linksys router (4-port...not wireless) and brought
>> it
>> > home to connect two pc's to the internet (shaw high speed).
>> > He previously had two NIC's in one computer and was using NAT software
> to

>> > share, therefore his *other* machine was connected using a crossover
>> > cable...
>> >
>> > He removed the second NIC, and plugged in one machine. No problem. He
>> > plugged the other machine into the "uplink" port on the router (and the
>> link
>> > lights came on), but he's unable to release and renew his IP address nor
>> > connect to the internet (duh.). (He's getting a 169.254.....)
>> >
>> > Though the crossover cable worked fine before, I suggested we make a
>> > straight through cable and try a regular port (...'cause what else is
>> there
>> > to try?!)
>> >
>> > I sliced off the ends of the crossover cable, and crimped on some
> straight
>> > thru ends.
>> >
>> > Still doesn't work.
>> >
>> > I tested the cable with an ohmeter, an (as I write this post) am
> connected
>> > to the internet with that very cable (it's about 30 ft)
>> >
>> > So what's the deal? Is this an inherent problem with Linksys routers?
>> I've
>> > got a D-LINK switch, and there doesn't seem to be a problem. Is there
> too
>> > much capacitance in the cable and Linksys doesn't use inductors to
> counter
>> > the signal?
>> >
>> > I don't know...!
>> >
>> > So I brought this cable to work and tried it on two more Linksys router
>> with
>> > the same problem.
>> > Link lights are on where they should be on, machine is set to DHCP, no
> IP

>> > address coming down the cable to the NIC - keep getting 169.254 blah
>> blah...
>> >
>> > Has anybody got the foggiest idea why this cable works on *some*
> equipment
>> > and not others?
>> >
>> > (BTW - "let the link light be your guide" doesn't cover this problem...
>> The
>> > link lights are responding the way it should...!)
>> >
>> > --
>> > JonnieStyle
>> > jonniestyle@hotmail.com
>> >
>> >
>>
>>
>

MCSEwannabe

2002-10-05, 11:23 pm

">Pearl Jam<" <dontcallme@home.com> wrote:

> Like I said... once a system goes bonkers and gives that kinda generic
> IP address... no matter what you do... you will NOT access the net or
> anything on the LAN or WAN... not even printers being shared...
>
> And like I said before... boot the pc to a C: prompt and run SCANREG
> /RESTORE ...then u select by date the best file u want to go back to
> and it will release that stupid IP... hence allowing you to
> reconfigure it.
>

The 169.254.x.x address is an AIPA address, automatically assigned when
the PC is set to 'obtain IP address automatically' but it can't reach a
DHCP server. Fix the connectivity problem that prevents it from seeing
the DHCP server and it will get the right IP address. No need for mucking
with registry restores.

>>PJ<
>
> On Sun, 29 Sep 2002 14:51:25 GMT, "JonnieStyle"
> <jonniestyle@hotmail.com> wrote:
>
>>I can't get into the router's setup though.
>>
>>That's the real problem. Opening a browser to http://192.168.1.1
>>opens a DNS error, and not the router's configuration.
>>The problem is the lights indicate there is a connection, but the
>>computer and NIC aren't connecting.
>>
>>(...and I've tried different computers and different Linksys routers -
>>the cable, however, works fine on other hardware...)
>>
>>Figure that one out!
>>
>>Cheers.
>>
>>"PC Trouble Shooter -->" <mkloch@pc-troubleshooter.com> wrote in
>>message news:Q1Dl9.3$xU3.7949@news.abs.net...
>>> Sounds like you need to clone the MAC address from the original NIC
>>> and
>>put
>>> it in the router. Reset cable modem & router all should work
>>> afterwards. The cable company binds to the MAc on the NIC when they
>>> set 'em up!
>>>
>>> Mark
>>>
>>> "JonnieStyle" <jonniestyle@hotmail.com> wrote in message
>>> news:9Hjl9.12075$bj5.611880@news2.telusplanet.net...
>>> > To recap:
>>> >
>>> > A guy I know bought a Linksys router (4-port...not wireless) and
>>> > brought
>>> it
>>> > home to connect two pc's to the internet (shaw high speed).
>>> > He previously had two NIC's in one computer and was using NAT
>>> > software
>>to
>>> > share, therefore his *other* machine was connected using a
>>> > crossover cable...
>>> >
>>> > He removed the second NIC, and plugged in one machine. No
>>> > problem. He plugged the other machine into the "uplink" port on
>>> > the router (and the
>>> link
>>> > lights came on), but he's unable to release and renew his IP
>>> > address nor connect to the internet (duh.). (He's getting a
>>> > 169.254.....)
>>> >
>>> > Though the crossover cable worked fine before, I suggested we make
>>> > a straight through cable and try a regular port (...'cause what
>>> > else is
>>> there
>>> > to try?!)
>>> >
>>> > I sliced off the ends of the crossover cable, and crimped on some
>>straight
>>> > thru ends.
>>> >
>>> > Still doesn't work.
>>> >
>>> > I tested the cable with an ohmeter, an (as I write this post) am
>>connected
>>> > to the internet with that very cable (it's about 30 ft)
>>> >
>>> > So what's the deal? Is this an inherent problem with Linksys
>>> > routers?
>>> I've
>>> > got a D-LINK switch, and there doesn't seem to be a problem. Is
>>> > there
>>too
>>> > much capacitance in the cable and Linksys doesn't use inductors to
>>counter
>>> > the signal?
>>> >
>>> > I don't know...!
>>> >
>>> > So I brought this cable to work and tried it on two more Linksys
>>> > router
>>> with
>>> > the same problem.
>>> > Link lights are on where they should be on, machine is set to
>>> > DHCP, no
>>IP
>>> > address coming down the cable to the NIC - keep getting 169.254
>>> > blah
>>> blah...
>>> >
>>> > Has anybody got the foggiest idea why this cable works on *some*
>>equipment
>>> > and not others?
>>> >
>>> > (BTW - "let the link light be your guide" doesn't cover this
>>> > problem...
>>> The
>>> > link lights are responding the way it should...!)
>>> >
>>> > --
>>> > JonnieStyle
>>> > jonniestyle@hotmail.com
>>> >
>>> >
>>>
>>>
>>
>
>

Barry Watzman

2002-10-06, 12:24 pm

I don't see that scanreg will fix this.

You can fix IP and DHCP problems by running IPCONFIG or WINIPCFG with
the option to release and renew all IP connections. The exact command
and syntax varies with the OS.

>Pearl Jam< wrote:
> Like I said... once a system goes bonkers and gives that kinda generic
> IP address... no matter what you do... you will NOT access the net or
> anything on the LAN or WAN... not even printers being shared...
>
> And like I said before... boot the pc to a C: prompt and run SCANREG
> /RESTORE ...then u select by date the best file u want to go back to
> and it will release that stupid IP... hence allowing you to
> reconfigure it.
>
>
>>PJ<
>
>
> On Sun, 29 Sep 2002 14:51:25 GMT, "JonnieStyle"
> <jonniestyle@hotmail.com> wrote:
>
>
>>I can't get into the router's setup though.
>>
>>That's the real problem. Opening a browser to http://192.168.1.1 opens a
>>DNS error, and not the router's configuration.
>>The problem is the lights indicate there is a connection, but the computer
>>and NIC aren't connecting.
>>
>>(...and I've tried different computers and different Linksys routers - the
>>cable, however, works fine on other hardware...)
>>
>>Figure that one out!
>>
>>Cheers.
>>
>>"PC Trouble Shooter -->" <mkloch@pc-troubleshooter.com> wrote in message
>>news:Q1Dl9.3$xU3.7949@news.abs.net...
>>
>>>Sounds like you need to clone the MAC address from the original NIC and
>>
>>put
>>
>>>it in the router. Reset cable modem & router all should work afterwards.
>>>The cable company binds to the MAc on the NIC when they set 'em up!
>>>
>>>Mark
>>>
>>>"JonnieStyle" <jonniestyle@hotmail.com> wrote in message
>>>news:9Hjl9.12075$bj5.611880@news2.telusplanet.net...
>>>
>>>>To recap:
>>>>
>>>>A guy I know bought a Linksys router (4-port...not wireless) and brought
>>>
>>>it
>>>
>>>>home to connect two pc's to the internet (shaw high speed).
>>>>He previously had two NIC's in one computer and was using NAT software
>>>
>>to
>>
>>>>share, therefore his *other* machine was connected using a crossover
>>>>cable...
>>>>
>>>>He removed the second NIC, and plugged in one machine. No problem. He
>>>>plugged the other machine into the "uplink" port on the router (and the
>>>
>>>link
>>>
>>>>lights came on), but he's unable to release and renew his IP address nor
>>>>connect to the internet (duh.). (He's getting a 169.254.....)
>>>>
>>>>Though the crossover cable worked fine before, I suggested we make a
>>>>straight through cable and try a regular port (...'cause what else is
>>>
>>>there
>>>
>>>>to try?!)
>>>>
>>>>I sliced off the ends of the crossover cable, and crimped on some
>>>
>>straight
>>
>>>>thru ends.
>>>>
>>>>Still doesn't work.
>>>>
>>>>I tested the cable with an ohmeter, an (as I write this post) am
>>>
>>connected
>>
>>>>to the internet with that very cable (it's about 30 ft)
>>>>
>>>>So what's the deal? Is this an inherent problem with Linksys routers?
>>>
>>>I've
>>>
>>>>got a D-LINK switch, and there doesn't seem to be a problem. Is there
>>>
>>too
>>
>>>>much capacitance in the cable and Linksys doesn't use inductors to
>>>
>>counter
>>
>>>>the signal?
>>>>
>>>>I don't know...!
>>>>
>>>>So I brought this cable to work and tried it on two more Linksys router
>>>
>>>with
>>>
>>>>the same problem.
>>>>Link lights are on where they should be on, machine is set to DHCP, no
>>>
>>IP
>>
>>>>address coming down the cable to the NIC - keep getting 169.254 blah
>>>
>>>blah...
>>>
>>>>Has anybody got the foggiest idea why this cable works on *some*
>>>
>>equipment
>>
>>>>and not others?
>>>>
>>>>(BTW - "let the link light be your guide" doesn't cover this problem...
>>>
>>>The
>>>
>>>>link lights are responding the way it should...!)
>>>>
>>>>--
>>>>JonnieStyle
>>>>jonniestyle@hotmail.com
>>>>
>>>>
>>>
>>>
>

JonnieStyle

2002-10-09, 5:24 pm

Nope. Wasn't the registry. T'was the cable.

How do I know? 'cause a different cable works fine.

">Pearl Jam<" <dontcallme@home.com> wrote in message
news:0ndvpucpn97mclq0splschjc9
r38ufh62r@4ax.com...
> Like I said... once a system goes bonkers and gives that kinda generic
> IP address... no matter what you do... you will NOT access the net or
> anything on the LAN or WAN... not even printers being shared...
>
> And like I said before... boot the pc to a C: prompt and run SCANREG
> /RESTORE ...then u select by date the best file u want to go back to
> and it will release that stupid IP... hence allowing you to
> reconfigure it.
>
> >PJ<
>
> On Sun, 29 Sep 2002 14:51:25 GMT, "JonnieStyle"
> <jonniestyle@hotmail.com> wrote:
>
> >I can't get into the router's setup though.
> >
> >That's the real problem. Opening a browser to http://192.168.1.1 opens a
> >DNS error, and not the router's configuration.
> >The problem is the lights indicate there is a connection, but the
computer
> >and NIC aren't connecting.
> >
> >(...and I've tried different computers and different Linksys routers -
the
> >cable, however, works fine on other hardware...)
> >
> >Figure that one out!
> >
> >Cheers.
> >
> >"PC Trouble Shooter -->" <mkloch@pc-troubleshooter.com> wrote in message
> >news:Q1Dl9.3$xU3.7949@news.abs.net...
> >> Sounds like you need to clone the MAC address from the original NIC and
> >put
> >> it in the router. Reset cable modem & router all should work
afterwards. [colo
r=darkred]
> >> The cable company binds to the MAc on the NIC when they set 'em up!
> >>
> >> Mark
> >>
> >> "JonnieStyle" <jonniestyle@hotmail.com> wrote in message
> >> news:9Hjl9.12075$bj5.611880@news2.telusplanet.net...
> >> > To recap:
> >> >
> >> > A guy I know bought a Linksys router (4-port...not wireless) and[/color]
brought
> >> it
> >> > home to connect two pc's to the internet (shaw high speed).
> >> > He previously had two NIC's in one computer and was using NAT
software
> >to
> >> > share, therefore his *other* machine was connected using a crossover
> >> > cable...
> >> >
> >> > He removed the second NIC, and plugged in one machine. No problem.
He[co
lor=darkred]
> >> > plugged the other machine into the "uplink" port on the router (and[/color]
the[c
olor=darkred]
> >> link
> >> > lights came on), but he's unable to release and renew his IP address[/color]
nor[c
olor=darkred]
> >> > connect to the internet (duh.). (He's getting a 169.254.....)
> >> >
> >> > Though the crossover cable worked fine before, I suggested we make a
> >> > straight through cable and try a regular port (...'cause what else is
> >> there
> >> > to try?!)
> >> >
> >> > I sliced off the ends of the crossover cable, and crimped on some
> >straight
> >> > thru ends.
> >> >
> >> > Still doesn't work.
> >> >
> >> > I tested the cable with an ohmeter, an (as I write this post) am
> >connected
> >> > to the internet with that very cable (it's about 30 ft)
> >> >
> >> > So what's the deal? Is this an inherent problem with Linksys[/color]
routers? [colo
r=darkred]
> >> I've
> >> > got a D-LINK switch,