I'm trying to connect an Me PC to a 2000 PC with a direct connection through a crossover ethernet cable. 2000 is happy enough with this and it can ping the ME machine with no problem, but the ME machine just refuses to have anything to do with it. The IP addresses are OK, the subnet masks are fine, no driver problems, they're both in the same workgroup with different names... But at the end of the day, it doesn't WORK! Why not?

Check all your firewalls, especially those bundled with virus scanners.


"wiffles" <(E-Mail Removed)> wrote in message
news:698E5BBA-80CA-4946-AF11-(E-Mail Removed)...
> I'm trying to connect an Me PC to a 2000 PC with a direct connection
through a crossover ethernet cable. 2000 is happy enough with this and it
can ping the ME machine with no problem, but the ME machine just refuses to
have anything to do with it. The IP addresses are OK, the subnet masks are
fine, no driver problems, they're both in the same workgroup with different
names... But at the end of the day, it doesn't WORK! Why not?

I believe you will have to use a hub to connect these two machines. A crossover cable won't
work due to the differences in the operating systems.

Thanks,
Gary
--------------------
'--'Thread-Topic: 2000 won't network with ME!
'--'thread-index: AcP3wxMg4M/gXk+EReWZ4BL7cqQPwA==
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'From: "=?Utf-8?B?d2lmZmxlcw==?=" <(E-Mail Removed)>
'--'Subject: 2000 won't network with ME!
'--'Date: Fri, 20 Feb 2004 07:06:10 -0800
'--'Lines: 1
'--'Message-ID: <698E5BBA-80CA-4946-AF11-(E-Mail Removed)>
'--'MIME-Version: 1.0
'--'Content-Type: text/plain;
'--' charset="Utf-8"
'--'Content-Transfer-Encoding: 7bit
'--'X-Newsreader: Microsoft CDO for Windows 2000
'--'Content-Class: urn:content-classes:message
'--'Importance: normal
'--'Priority: normal
'--'X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
'--'Newsgroups: microsoft.public.win2000.networking
'--'Path: cpmsftngxa07.phx.gbl
'--'Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:55471
'--'NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'
'--'I'm trying to connect an Me PC to a 2000 PC with a direct connection through a crossover
ethernet cable. 2000 is happy enough with this and it can ping the ME machine with no
problem, but the ME machine just refuses to have anything to do with it. The IP addresses are
OK, the subnet masks are fine, no driver problems, they're both in the same workgroup with
different names... But at the end of the day, it doesn't WORK! Why not?
'--'

Not at all. Networking connectivity occurs at a much
lower layer than operating systems. You can connect
any Windows machine with any other Windows machine,
with or without a hub.

Your statement is equivalent to saying that you need a
different phone when talking to someone in a different
language.


"Gary Fose [MSFT]" <(E-Mail Removed)> wrote in message
news:j7KlbgN%(E-Mail Removed)...
> I believe you will have to use a hub to connect these two machines. A
crossover cable won't
> work due to the differences in the operating systems.
>
> Thanks,
> Gary
> --------------------
> '--'Thread-Topic: 2000 won't network with ME!
> '--'thread-index: AcP3wxMg4M/gXk+EReWZ4BL7cqQPwA==
> '--'X-Tomcat-NG: microsoft.public.win2000.networking
> '--'From: "=?Utf-8?B?d2lmZmxlcw==?=" <(E-Mail Removed)>
> '--'Subject: 2000 won't network with ME!
> '--'Date: Fri, 20 Feb 2004 07:06:10 -0800
> '--'Lines: 1
> '--'Message-ID: <698E5BBA-80CA-4946-AF11-(E-Mail Removed)>
> '--'MIME-Version: 1.0
> '--'Content-Type: text/plain;
> '--' charset="Utf-8"
> '--'Content-Transfer-Encoding: 7bit
> '--'X-Newsreader: Microsoft CDO for Windows 2000
> '--'Content-Class: urn:content-classes:message
> '--'Importance: normal
> '--'Priority: normal
> '--'X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> '--'Newsgroups: microsoft.public.win2000.networking
> '--'Path: cpmsftngxa07.phx.gbl
> '--'Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:55471
> '--'NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
> '--'X-Tomcat-NG: microsoft.public.win2000.networking
> '--'
> '--'I'm trying to connect an Me PC to a 2000 PC with a direct connection
through a crossover
> ethernet cable. 2000 is happy enough with this and it can ping the ME
machine with no
> problem, but the ME machine just refuses to have anything to do with it.
The IP addresses are
> OK, the subnet masks are fine, no driver problems, they're both in the
same workgroup with
> different names... But at the end of the day, it doesn't WORK! Why not?
> '--'
>
>

Get rid of ME!!!


"wiffles" <(E-Mail Removed)> wrote in message
news:698E5BBA-80CA-4946-AF11-(E-Mail Removed)...
> I'm trying to connect an Me PC to a 2000 PC with a direct connection
through a crossover ethernet cable. 2000 is happy enough with this and it
can ping the ME machine with no problem, but the ME machine just refuses to
have anything to do with it. The IP addresses are OK, the subnet masks are
fine, no driver problems, they're both in the same workgroup with different
names... But at the end of the day, it doesn't WORK! Why not?

Good point, even though I don't think that ME is to blame
in this case.


"Adam" <(E-Mail Removed)> wrote in message
news:joadnZGJSOAGHaTdRVn-(E-Mail Removed)...
> Get rid of ME!!!
>
>
> "wiffles" <(E-Mail Removed)> wrote in message
> news:698E5BBA-80CA-4946-AF11-(E-Mail Removed)...
> > I'm trying to connect an Me PC to a 2000 PC with a direct connection
> through a crossover ethernet cable. 2000 is happy enough with this and it
> can ping the ME machine with no problem, but the ME machine just refuses
to
> have anything to do with it. The IP addresses are OK, the subnet masks are
> fine, no driver problems, they're both in the same workgroup with
different
> names... But at the end of the day, it doesn't WORK! Why not?
>
>

Try this:

1) Creat a new user different from the one that you are
logged on to the Windows 2000 Professional box with.
Create this account on both the Windows 2000 Pro box
and the Windows ME device.

2) Grant administrator's rights to both accounts on both
boxes.

3) Now you will be able to connect to shares on the Windows 2000 Pro
box from the Windows ME device using the Null Modem connection.

Hope this helps,
Gary

--------------------
'--'From: "Pegasus \(MVP\)" <(E-Mail Removed)>
'--'Newsgroups: microsoft.public.win2000.networking
'--'Subject: Re: 2000 won't network with ME!
'--'Date: Mon, 23 Feb 2004 15:34:22 +1100
'--'Organization: Keypoint
'--'Lines: 23
'--'Message-ID: <c1bvs1$1h9o$(E-Mail Removed)>
'--'References: <698E5BBA-80CA-4946-AF11-(E-Mail Removed)>
<joadnZGJSOAGHaTdRVn-(E-Mail Removed)>
'--'NNTP-Posting-Host: dsl262-mlb.keypoint.com.au
'--'X-Trace: arachne.labyrinth.net.au 1077510849 50488 202.182.75.49 (23 Feb 2004 04:34:09
GMT)
'--'X-Complaints-To: (E-Mail Removed)
'--'NNTP-Posting-Date: Mon, 23 Feb 2004 04:34:09 +0000 (UTC)
'--'X-Priority: 3
'--'X-MSMail-Priority: Normal
'--'X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
'--'X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
'--'Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-
online.de!newsfeed.gamma.ru!Gamma.RU!news-out.visi.com!petbe.visi.com!
news.octanews.net!news1.optus.net.au!optus!news.mel.connect.com.au!
news.netspace.net.au!news.labyrinth.net.au!not-for-mail
'--'Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.networking:56177
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'
'--'Good point, even though I don't think that ME is to blame
'--'in this case.
'--'
'--'
'--'"Adam" <(E-Mail Removed)> wrote in message
'--'news:joadnZGJSOAGHaTdRVn-(E-Mail Removed)...
'--'> Get rid of ME!!!
'--'>
'--'>
'--'> "wiffles" <(E-Mail Removed)> wrote in message
'--'> news:698E5BBA-80CA-4946-AF11-(E-Mail Removed)...
'--'> > I'm trying to connect an Me PC to a 2000 PC with a direct connection
'--'> through a crossover ethernet cable. 2000 is happy enough with this and it
'--'> can ping the ME machine with no problem, but the ME machine just refuses
'--'to
'--'> have anything to do with it. The IP addresses are OK, the subnet masks are
'--'> fine, no driver problems, they're both in the same workgroup with
'--'different
'--'> names... But at the end of the day, it doesn't WORK! Why not?
'--'>
'--'>
'--'
'--'
'--'


This posting is provided "AS IS" with no warranties, and confers no rights. Use of included
script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best
directed to the newsgroup/thread from which they originated.

Just an idea:
Maybe the W2k requires stronger authentication than the ME can do.
Take a look at the sec. logs and the sec. policy

Br Miklos


"Pegasus (MVP)" <(E-Mail Removed)> az alábbiakat írta a következo üzenetben
news:c1bvs1$1h9o$(E-Mail Removed)...
> Good point, even though I don't think that ME is to blame
> in this case.
>
>
> "Adam" <(E-Mail Removed)> wrote in message
> news:joadnZGJSOAGHaTdRVn-(E-Mail Removed)...
> > Get rid of ME!!!
> >
> >
> > "wiffles" <(E-Mail Removed)> wrote in message
> > news:698E5BBA-80CA-4946-AF11-(E-Mail Removed)...
> > > I'm trying to connect an Me PC to a 2000 PC with a direct connection
> > through a crossover ethernet cable. 2000 is happy enough with this and
it
> > can ping the ME machine with no problem, but the ME machine just refuses
> to
> > have anything to do with it. The IP addresses are OK, the subnet masks
are
> > fine, no driver problems, they're both in the same workgroup with
> different
> > names... But at the end of the day, it doesn't WORK! Why not?
> >
> >
>
>