[Lvlug] One Machine on Network can't see TCP/IP 192.168.0.1 (or .sometime...
LFessen106@aol.com
LFessen106@aol.com
Mon, 17 Dec 2001 13:08:35 EST
--part1_b7.189c1f62.294f8ea3_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 12/17/01 12:51:15 PM Eastern Standard Time,
rhkramer@fast.net writes:
> Only thing I can think of is that the card in the new machine is flaky,
> but, so far, I haven't seen any strange results when viewing stuff on
> the LAN or on the Internet.
>
> Any other theories?
Sounds to me like your card is bad.. You might want to check the bnc
connector for crud or corrosion on the card it'self and also maybe replace
the 'T' connector at that joint.
-Linc.
In The Beginning there was nothing, which exploded - Yeah right...
Calculating in binary code is as easy as 01,10,11.
--part1_b7.189c1f62.294f8ea3_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
<HTML><FONT FACE=arial,helvetica><FONT SIZE=2>In a message dated 12/17/01 12:51:15 PM Eastern Standard Time, rhkramer@fast.net writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Only thing I can think of is that the card in the new machine is flaky,
<BR>but, so far, I haven't seen any strange results when viewing stuff on
<BR>the LAN or on the Internet.
<BR>
<BR>Any other theories? </BLOCKQUOTE>
<BR>
<BR>
<BR>Sounds to me like your card is bad.. You might want to check the bnc connector for crud or corrosion on the card it'self and also maybe replace the 'T' connector at that joint.
<BR>
<BR>-Linc.
<BR>
<BR>In The Beginning there was nothing, which exploded - Yeah right...
<BR>
<BR>Calculating in binary code is as easy as 01,10,11.</FONT></HTML>
--part1_b7.189c1f62.294f8ea3_boundary--