Can't connect computers with hub or cross LAN cable

Hi,

I met on serious problem with my computers. I have one desktop & one
notebook both with windows ME installed. Each of which has a LAN card
installed. I could use each of them to browse internet separately (IP
auto assigned from ISP).

However, as I connected them to my LAN hub AND configured different
IPs, both of them couldn't ping the other so they couldn't
communicate. I observed my LAN hub LED. When ping command was typed,
the packet LED flashed. Other LAN hub LED also worked normal. The same
situation happened when I connected them with cross LAN cable.

I have checked the manual configured IP addresses & subnet mask, no
conflict.

I don't have any cable tester to test the LAN cables but those 3
cables (2 straight, one cross) had been used previously with no
problem.

Could anyone advise what should be checked / tested to further
diagnose the problem ?

Tks!

reset both lan and modem pull power on the hub/switch/router and
the modem
"Emil Lam" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Hi,
>
> I met on serious problem with my computers. I have one desktop & one
> notebook both with windows ME installed. Each of which has a LAN
card
> installed. I could use each of them to browse internet separately
(IP
> auto assigned from ISP).
>
> However, as I connected them to my LAN hub AND configured different
> IPs, both of them couldn't ping the other so they couldn't
> communicate. I observed my LAN hub LED. When ping command was typed,
> the packet LED flashed. Other LAN hub LED also worked normal. The
same
> situation happened when I connected them with cross LAN cable.
>
> I have checked the manual configured IP addresses & subnet mask, no
> conflict.
>
> I don't have any cable tester to test the LAN cables but those 3
> cables (2 straight, one cross) had been used previously with no
> problem.
>
> Could anyone advise what should be checked / tested to further
> diagnose the problem ?
>
> Tks!

Try here http://www.careyholzman.com/netfixes.htm or here
http://www.practicallynetworked.com/.../troubleshoot/

"Emil Lam" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Hi,
>
> I met on serious problem with my computers. I have one desktop & one
> notebook both with windows ME installed. Each of which has a LAN card
> installed. I could use each of them to browse internet separately (IP
> auto assigned from ISP).
>
> However, as I connected them to my LAN hub AND configured different
> IPs, both of them couldn't ping the other so they couldn't
> communicate. I observed my LAN hub LED. When ping command was typed,
> the packet LED flashed. Other LAN hub LED also worked normal. The same
> situation happened when I connected them with cross LAN cable.
>
> I have checked the manual configured IP addresses & subnet mask, no
> conflict.
>
> I don't have any cable tester to test the LAN cables but those 3
> cables (2 straight, one cross) had been used previously with no
> problem.
>
> Could anyone advise what should be checked / tested to further
> diagnose the problem ?
>
> Tks!

Emil Lam wrote:
> Could anyone advise what should be checked / tested to further
> diagnose the problem ?

Does your ISP provide multiple IPs?

If not, then you need a router, not a hub.

In article <(E-Mail Removed) >,
(E-Mail Removed) (Emil Lam) wrote:
>Hi,
>
>I met on serious problem with my computers. I have one desktop & one
>notebook both with windows ME installed. Each of which has a LAN card
>installed. I could use each of them to browse internet separately (IP
>auto assigned from ISP).
>
>However, as I connected them to my LAN hub AND configured different
>IPs, both of them couldn't ping the other so they couldn't
>communicate. I observed my LAN hub LED. When ping command was typed,
>the packet LED flashed. Other LAN hub LED also worked normal. The same
>situation happened when I connected them with cross LAN cable.
>
>I have checked the manual configured IP addresses & subnet mask, no
>conflict.
>
>I don't have any cable tester to test the LAN cables but those 3
>cables (2 straight, one cross) had been used previously with no
>problem.
>
>Could anyone advise what should be checked / tested to further
>diagnose the problem ?
>
>Tks!

To ping each other and communicate via TCP/IP, the computers must have
IP addresses in the same subnet. If they get their IP addresses from
your ISP, it's possible that they're in different subnets.

If your ISP is assigning public IP addresses to both computers, then
it probably isn't safe to use TCP/IP for file sharing, because other
Internet users might be able to access your files. They're public IP
addresses if they're NOT in these ranges:

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

If they have public IP addresses, then you need to take steps to share
files safely. Possibilities include:

1. Replacing the hub with a broadband router, which assigns private IP
addresses to the computers.

2. Installing a second network adapter in one of the computers,
connecting it directly to the Internet, and enabling Internet
Connection Sharing on the second network adapter.

3. Installing a another protocol (either IPX/SPX or NetBEUI) on both
computers and un-binding file sharing from TCP/IP.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> To ping each other and communicate via TCP/IP, the computers must have
> IP addresses in the same subnet. If they get their IP addresses from
> your ISP, it's possible that they're in different subnets.
>

Bullshit. You do /not/ need to be in the same subnet to ping each other,
case in point:
IP Address. . . . . . . . . . . . : 209.204.68.239
Subnet Mask . . . . . . . . . . . : 255.255.255.0

Pinging www.google.akadns.net [216.239.39.99] with 32 bytes of data:

Reply from 216.239.39.99: bytes=32 time=9ms TTL=242

Clearly 216.239.39.99 is not in my subnet.

I do understand your point though, I'm just being anal.

In article <(E-Mail Removed)>, Steve Winograd
[MVP] says...

> If your ISP is assigning public IP addresses to both computers, then
> it probably isn't safe to use TCP/IP for file sharing, because other
> Internet users might be able to access your files. They're public IP
> addresses if they're NOT in these ranges:

> 10.0.0.0 - 10.255.255.255
> 172.16.0.0 - 172.31.255.255
> 192.168.0.0 - 192.168.255.255

As well:

0.0.0.0 - 0.255.255.255 (IANA reserved; see RFC 3330)
127.0.0.0 - 127.255.255.255 (Loopback; see RFC 3330)
169.254.0.0 - 169.254.255.255 (LinkLocal; see RFC 3330)
224.0.0.0 - 255.255.255.255 (spans more than one range reserved by IANA for
special use; see RFC 3171 and RFC 3330)

None of the above should be routed publicly.

--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

In article <(E-Mail Removed)> , Norman
Miller <(E-Mail Removed)> wrote:
>In article <(E-Mail Removed)>, Steve Winograd
>[MVP] says...
>
>> If your ISP is assigning public IP addresses to both computers, then
>> it probably isn't safe to use TCP/IP for file sharing, because other
>> Internet users might be able to access your files. They're public IP
>> addresses if they're NOT in these ranges:
>
>> 10.0.0.0 - 10.255.255.255
>> 172.16.0.0 - 172.31.255.255
>> 192.168.0.0 - 192.168.255.255
>
>As well:
>
>0.0.0.0 - 0.255.255.255 (IANA reserved; see RFC 3330)
>127.0.0.0 - 127.255.255.255 (Loopback; see RFC 3330)
>169.254.0.0 - 169.254.255.255 (LinkLocal; see RFC 3330)
>224.0.0.0 - 255.255.255.255 (spans more than one range reserved by IANA for
>special use; see RFC 3171 and RFC 3330)
>
>None of the above should be routed publicly.

An ISP can't assign an IP address in the ranges that you mentioned,
Norman -- those ranges are reserved for special purposes and aren't
routeable.

Only the LinkLocal block can be used on a LAN, and then only if there
isn't a DHCP server on the LAN.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

Dear all,

I got the cause. The connection was back to normal after I disabled
norton internet security at both computers (NIS 2003 ran at desktop
side & NIS 2004 ran at notebook side).

However, the problem didn't get solved because it was not a good
solution. I didn't know which NIS setting caused this. Actually these
NIS had been running long ago and both computers could communicate
over LAN.

All the thing I did recently was getting live update from norton site
few days ago (that NIS 2003 didn't get update for over one month
before this problem was found).

Could anyone familiar with NIS give me some suggestion ?

Remark: I just use default settings for both NIS versions.

Best suggestion you're likely to get from anyone in these groups is to
uninstall NIS and get something that works with Win9x systems!

--
Noel Paton (MS-MVP 2002-2005, Windows)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Emil Lam" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Dear all,
>
> I got the cause. The connection was back to normal after I disabled
> norton internet security at both computers (NIS 2003 ran at desktop
> side & NIS 2004 ran at notebook side).
>
> However, the problem didn't get solved because it was not a good
> solution. I didn't know which NIS setting caused this. Actually these
> NIS had been running long ago and both computers could communicate
> over LAN.
>
> All the thing I did recently was getting live update from norton site
> few days ago (that NIS 2003 didn't get update for over one month
> before this problem was found).
>
> Could anyone familiar with NIS give me some suggestion ?
>
> Remark: I just use default settings for both NIS versions.