Windows ME networked with Windows XP Pro - DHCP...

[C D]

Hi guys,

I have a desktop pc (running windows ME) connected to a laptop via an
ethernet cable. The Laptop has a broadband connection and I am running
internet connection sharing.
My question is, will WinME hang if it can not renew its address from the
DHCP server, on the laptop? Will any NIC related problems cause WinME to
hang?

Cheers.
Clive

[Mike M]

Clive,

If when booting Win Me cannot see the DHCP server bootup will be delayed
somewhat after which the NIC will be automatically assigned a private address
after which no further delays should be experienced unless you attempt to
access the laptop for some reason. I can't for the life of me remember the
block of private IP addresses used but it is not the 192.168.x.x block used by
Internet Connection Sharing nor as far as I recall the 10.x.x.x block which I
suppose then means it has to be one between 192.168.0.0 through
192.168.255.255 but cannot be sure about that.
--
Mike Maltby MS-MVP



C D > wrote:

> Hi guys,
>
> I have a desktop pc (running windows ME) connected to a laptop via an
> ethernet cable. The Laptop has a broadband connection and I am running
> internet connection sharing.
> My question is, will WinME hang if it can not renew its address from
> the DHCP server, on the laptop? Will any NIC related problems cause
> WinME to hang?

[C D]

Hi Mike,

I am just trying to troubleshoot why Windows ME is hanging on me, and this
could be a possibility. Basically I have 3 machines, but at any one time
only two are connected together, one of which has to be the laptop, as it is
connected to the internet.

I own two dekstop pcs and one laptop pc. One desktop pc runs XP pro, the
other Win ME and the laptop XP Pro.

Yesterday, I had the WinME+WinXP combination, and the machine would lock
up. It would see the internet
ok for a time, but then after a while, everything would freeze and I would
have to do a manual reset.

When I had the WinXP+WinXP combination, I discovered that the desktop pc was
having problems renewing its address from the DHCP server on the laptop . So the WinXP desktop
doesn't fall over when the DHCP address cannot be renewed, after startup,
but will the WinME one fall over?

Cheers,

Clive

"Mike M" > wrote in message
...
> Clive,
>
> If when booting Win Me cannot see the DHCP server bootup will be delayed
> somewhat after which the NIC will be automatically assigned a private
address
> after which no further delays should be experienced unless you attempt to
> access the laptop for some reason. I can't for the life of me remember
the
> block of private IP addresses used but it is not the 192.168.x.x block
used by
> Internet Connection Sharing nor as far as I recall the 10.x.x.x block
which I
> suppose then means it has to be one between 192.168.0.0 through
> 192.168.255.255 but cannot be sure about that.
> --
> Mike Maltby MS-MVP
>
>
>
> C D > wrote:
>[i]
> > Hi guys,
> >
> > I have a desktop pc (running windows ME) connected to a laptop via an
> > ethernet cable. The Laptop has a broadband connection and I am running
> > internet connection sharing.
> > My question is, will WinME hang if it can not renew its address from
> > the DHCP server, on the laptop? Will any NIC related problems cause
> > WinME to hang?
>

[Mike M]

Correction - I meant to say:
"which I suppose then means it has to be one between 172.16.0.0 through
172.31.255.255 but cannot be sure about that."
--
Mike Maltby MS-MVP



Mike M > wrote:

> Clive,
>
> If when booting Win Me cannot see the DHCP server bootup will be
> delayed somewhat after which the NIC will be automatically assigned a
> private address after which no further delays should be experienced
> unless you attempt to access the laptop for some reason. I can't for
> the life of me remember the block of private IP addresses used but it
> is not the 192.168.x.x block used by Internet Connection Sharing nor
> as far as I recall the 10.x.x.x block which I suppose then means it
> has to be one between 192.168.0.0 through 192.168.255.255 but cannot
> be sure about that.

[Mike M]

> So
> the WinXP desktop doesn't fall over when the DHCP address cannot be
> renewed, after startup, but will the WinME one fall over?

Not that I have ever seen here but I appreciate the experience of others may
differ. Hopefully someone more experienced with troubleshooting networking
problems will be able to chip in with their experiences.
--
Mike Maltby MS-MVP



C D > wrote:

> Hi Mike,
>
> I am just trying to troubleshoot why Windows ME is hanging on me, and
> this could be a possibility. Basically I have 3 machines, but at any
> one time only two are connected together, one of which has to be the
> laptop, as it is connected to the internet.
>
> I own two dekstop pcs and one laptop pc. One desktop pc runs XP pro,
> the other Win ME and the laptop XP Pro.
>
> Yesterday, I had the WinME+WinXP combination, and the machine would
> lock up. It would see the internet
> ok for a time, but then after a while, everything would freeze and I
> would have to do a manual reset.
>
> When I had the WinXP+WinXP combination, I discovered that the desktop
> pc was having problems renewing its address from the DHCP server on
> the laptop [I looked at event viewed in XP Pro on the desktop]. So
> the WinXP desktop doesn't fall over when the DHCP address cannot be
> renewed, after startup, but will the WinME one fall over?

[N. Miller]

In article >, Mike M says...

> If when booting Win Me cannot see the DHCP server bootup will be delayed
> somewhat after which the NIC will be automatically assigned a private address
> after which no further delays should be experienced unless you attempt to
> access the laptop for some reason. I can't for the life of me remember the
> block of private IP addresses used but it is not the 192.168.x.x block used by
> Internet Connection Sharing nor as far as I recall the 10.x.x.x block which I
> suppose then means it has to be one between 192.168.0.0 through
> 192.168.255.255 but cannot be sure about that.

It is not any of the RFC 1918 addresses reserved for private use. It is one
of the RFC 3330 addresses reserved for "Linklocal"; 169.254.0.0/16.


07/04/04 14:31:47 IP block
Trying 169.254.127.128 at ARIN
Trying 169.254.127 at ARIN

OrgName: Internet Assigned Numbers Authority
OrgID: IANA
Address: 4676 Admiralty Way, Suite 330
City: Marina del Rey
StateProv: CA
PostalCode: 90292-6695
Country: US

NetRange: 169.254.0.0 - 169.254.255.255
CIDR: 169.254.0.0/16
NetName: LINKLOCAL
NetHandle: NET-169-254-0-0-1
Parent: NET-169-0-0-0-0
NetType: IANA Special Use
NameServer: BLACKHOLE-1.IANA.ORG
NameServer: BLACKHOLE-2.IANA.ORG
Comment: Please see RFC 3330 for additional information.
RegDate: 1998-01-27
Updated: 2002-10-14

OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName: Internet Corporation for Assigned Names and Number
OrgAbusePhone: +1-310-301-5820
OrgAbuseEmail:

OrgTechHandle: IANA-IP-ARIN
OrgTechName: Internet Corporation for Assigned Names and Number
OrgTechPhone: +1-310-301-5820
OrgTechEmail:

# ARIN WHOIS database, last updated 2004-07-03 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.

--
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

[Mike M]

Thanks,

I knew it wasn't the 192.168.x.x or 10.x.x.x block and didn't really think it
was the 172.16.0.0 through
172.31.255.255. Now I see you post the IP range used my memory comes flooding
back. :-)
--
Mike Maltby MS-MVP



N. Miller > wrote:

> In article >, Mike M says...
>
>> If when booting Win Me cannot see the DHCP server bootup will be
>> delayed somewhat after which the NIC will be automatically assigned
>> a private address after which no further delays should be
>> experienced unless you attempt to access the laptop for some reason.
>> I can't for the life of me remember the block of private IP
>> addresses used but it is not the 192.168.x.x block used by Internet
>> Connection Sharing nor as far as I recall the 10.x.x.x block which I
>> suppose then means it has to be one between 192.168.0.0 through
>> 192.168.255.255 but cannot be sure about that.
>
> It is not any of the RFC 1918 addresses reserved for private use. It
> is one of the RFC 3330 addresses reserved for "Linklocal";
> 169.254.0.0/16.