Re: Unable to access internet from windows ME client on ICS

From: CFF (cffung_at_myrealbox.com)
Date: 09/17/04 

Date: 17 Sep 2004 07:15:59 -0700

"Babak" <Babak@Ershadifar.com> wrote in message news:<uJhnaAJnEHA.2764@TK2MSFTNGP10.phx.gbl>...
> This address generate with windows !
> I guess that ICS Pass 192.168.0.x for this adapter.
> "Autoconfiguration IP Address. . . : 169.254.227.13"
>
>
>
> "CFF" <cffung@myrealbox.com> wrote in message
> news:2560187f.0409162309.449da513@posting.google.com...
> > I have the following hardware setup intended for home based ICS but
> > fail to work.
> > To simplify the description of the configuration, I label these
> > components as
> > A, B, C, D, E and F.
> >
> > A B C D
> > +----------+ +------+ +----------------+ +------+
> > |external | |Intel | |Windows 2000 Pro| |D-Link|
> > Phone line----|LAN based |---|PCI |---|Host Machine |---|PCI
> > |----+
> |ADSL modem| |10/100| | | |10/100|
> > |
> +----------+ +------+ +----------------+ +------+
> > |
>
> > |
> +----------+ +-------+
> > |
> |Windows ME| |CardBus|
> > |
> |Client |------|PCMCI
> > |--------------------------------+
> > |Machine | |10/100 |
> > +----------+ +-------+
> > F E
> >
> > When I did a ipconfig /all, I got the following:
> >
> > Windows 2000 IP Configuration
> >
> > Host Name . . . . . . . . . . . . : host
> > Primary DNS Suffix . . . . . . . :
> > Node Type . . . . . . . . . . . . : Broadcast
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : No
> >
> > Ethernet adapter Local Area Connection: (i.e. BLOCK D)
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : D-Link DFE-538TX 10/100 Adapter
> > Physical Address. . . . . . . . . : 00-50-BA-50-28-68
> > DHCP Enabled. . . . . . . . . . . : Yes
> > Autoconfiguration Enabled . . . . : Yes
> > Autoconfiguration IP Address. . . : 169.254.227.13
> > Subnet Mask . . . . . . . . . . . : 255.255.0.0
> > Default Gateway . . . . . . . . . :
> > DNS Servers . . . . . . . . . . . :
> >
> > Ethernet adapter Local Area Connection 2: (i.e. BLOCK B)
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI Adapter
> > Physical Address. . . . . . . . . : 00-03-47-40-45-8C
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.0.1
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . :
> > DNS Servers . . . . . . . . . . . :
> >
> > PPP adapter WinPoET v5.0 Connection: (i.e. BLOCK A)
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> > Physical Address. . . . . . . . . : 00-53-45-00-00-00
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 220.255.54.71
> > Subnet Mask . . . . . . . . . . . : 255.255.255.255
> > Default Gateway . . . . . . . . . : 220.255.54.71
> > DNS Servers . . . . . . . . . . . : 165.21.83.88
> > 165.21.100.88
> >
> > The IP address (192.168.0.1) on BLOCK B is manually set. BLOCK D is
> > the
> > interface that is being shared. I've also tried to share either BLOCK
> > B
> > or BLOCK A instead but doing a ping the default gateway results in
> > request timed out. So, I am assuming BLOCK D is the right interface to
> > be
> > shared for the time being. Somebody can correct me if I am wrong.
> >
> >
> >
> > When I did an ipconfig on my client machine (BLOCK F), I got the
> > following:
> >
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . : RADIANT
> > DNS Servers . . . . . . . . : 192.168.0.1
> > Node Type . . . . . . . . . : Mixed
> > NetBIOS Scope ID. . . . . . :
> > IP Routing Enabled. . . . . : No
> > WINS Proxy Enabled. . . . . : No
> > NetBIOS Resolution Uses DNS : No
> >
> > 0 Ethernet adapter :
> >
> > Description . . . . . . . . : CardBus 10/100 Fast Ethernet Adapter
> > NDIS3 Driver
> > Physical Address. . . . . . : 00-E0-98-BE-29-6A
> > DHCP Enabled. . . . . . . . : Yes
> > IP Address. . . . . . . . . : 192.168.0.10
> > Subnet Mask . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . : 192.168.0.1
> > DHCP Server . . . . . . . . : 192.168.0.1
> > Primary WINS Server . . . . :
> > Secondary WINS Server . . . :
> > Lease Obtained. . . . . . . : 09 17 04 9:58:41 AM
> > Lease Expires . . . . . . . : 09 24 04 9:58:41 AM
> >
> > 1 Ethernet adapter :
> >
> > Description . . . . . . . . : PPP Adapter.
> > Physical Address. . . . . . : 44-45-53-54-00-00
> > DHCP Enabled. . . . . . . . : Yes
> > IP Address. . . . . . . . . : 0.0.0.0
> > Subnet Mask . . . . . . . . : 0.0.0.0
> > Default Gateway . . . . . . :
> > DHCP Server . . . . . . . . : 255.255.255.255
> > Primary WINS Server . . . . :
> > Secondary WINS Server . . . :
> > Lease Obtained. . . . . . . :
> > Lease Expires . . . . . . . :
> >
> > There is no problem at all when accessing internet on the host machine
> > but
> > fail to load any web page when operating on the client machine. What I
> > need to know is:
> >
> > 1) Out of the three interfaces displayed under Network and Dial-up
> > Connections, which is the right interface on the host to be shared?
> >
> > 2) what is the right procedure for verifying the connection between
> > host and
> > client? Would it suffice to do a ping on both machine? As mentioned, I
> > can
> > ping the default gateway on the client successfully but fail to load
> > web page.
> >
> > 3) Assumming 1) and 2) are ok, would it be reasonable to suspect the
> > problem
> > came from the host due of incompatibility problem of PPPoE? I am
> > saying this
> > because I can't get ping -f -l 1500 to work but lower MTU numbers.
> >
> > Having mentioned the above, all I want to do now is to isolate the
> > problem so
> > that I can proceed to sort it out the particular issue. Right now, I
> > have no
> > clue on what can I do next even though I've been playing with lots of
> > different settings without success. Can somebody help please?

Thank you for your help. I've just been able to sort out by sharing
the PPPoE connection with the Intel NIC. So, it is working now after
days of long struggling.

Relevant Pages

  • RE: ICS clients cannot connect
    ... I've got this from the ICS host: ... I turned off ICS host and then enabled it. ... the client and entered "ipconfig /release". ... goto one of the client machines and do the same, ...
    (microsoft.public.windowsxp.general)
  • Re: Getting Windows XP To Act as NAT Server
    ... ICS is a Windows XP NAT ROUTER solution - not NAT server. ... solution that would work on a Windows XP host? ...
    (microsoft.public.windowsxp.network_web)
  • Re: Why is SP2 so big? It doesnt do much
    ... >>the client machines to it as the router. ... >>That's what I mean about Windows being more tightly integrated. ... I'd have to set up a machine specifically for the 'built in ICS' ... configuration because I'm using Win2K server with Routing and Remote Access ...
    (microsoft.public.windowsxp.general)
  • Re: Networking snag with no internet on Client
    ... >>I can't get out on the internet, ... >Configure the 2000 machine as an ICS host as shown here, ... >Configure the XP machine as an ICS client as shown here: ...
    (microsoft.public.windowsxp.network_web)
  • ICS / (DNS?) Problem with Sharing Client
    ... I'm having a problem with ICS on Windows 2000 Pro. ... I use a 56k dial-up connection to my ISP on the ICS host. ... ethernet connection between the ICS host and the ICS client. ... Persistent Routes: ...
    (microsoft.public.win2000.networking)