"SEFL" <a***@searchenginefriendlylayouts.com> wrote in message
news:1157724899.572217.53160@m73g2000cwd.googlegroups.com...
> This is going to sound like a rather strange problem, but here goes:
>
> I've got a TrendNet TEW-432BRP wireless router and four computers
> trying to access it.  Here's the scenario of issues (one of which was
> solved, and I have no idea why):
>
> 1)  When the router was connected, domains would resolve to IP
> addresses (e.g. Google.ca to 64.233.161.104) but only a few sites would
> be accessible via a web browser.  I "solved" this by cloning the MAC
> address of the one machine that was wired into the router.  Why this
> worked, I have absolutely no idea, but it did.
>
> 2) NICs (both wired and wireless) will detect the router/network, and I
> am able to connect to it and log in using the WEP key.  The problem
> comes when assigning an IP address through DHCP...sometimes it takes an
> extremely long time (over a minute) and sometimes no IP address is
> assigned at all.  If I disconnect and reconnect the NIC to the router
> (in other words, repeat the process), most of the time I'll get an IP.
> Sometimes I have to do this 3-4 times before it works.
>
> The question I have is...why is this occurring?  Is this (as I suspect)
> a bad router, since it does work eventually?  Or is this something
> else?
>
> Thanks,
>
>
>
> Adam
> http://www.searchenginefriendlylayouts.com/
>

> Hi
>
> A1.  Without cloning the MAC you cannot go on to your services, it is like
> the ID and Pas Word.  The few pages that you saw are probably cached on your
> hard drive a while ago.
>
> A2. I do not know what WEP as to do with DHCP and assigning IPs?
>
> Try to fix your Network Stacks by doing the follow,
> http://www.ezlan.net/clean#refreshnet
>
> Jack (MVP-Networking).
>
>
> "SEFL" <a***@searchenginefriendlylayouts.com> wrote in message
> news:1157724899.572217.53160@m73g2000cwd.googlegroups.com...
> > This is going to sound like a rather strange problem, but here goes:
> >
> > I've got a TrendNet TEW-432BRP wireless router and four computers
> > trying to access it.  Here's the scenario of issues (one of which was
> > solved, and I have no idea why):
> >
> > 1)  When the router was connected, domains would resolve to IP
> > addresses (e.g. Google.ca to 64.233.161.104) but only a few sites would
> > be accessible via a web browser.  I "solved" this by cloning the MAC
> > address of the one machine that was wired into the router.  Why this
> > worked, I have absolutely no idea, but it did.
> >
> > 2) NICs (both wired and wireless) will detect the router/network, and I
> > am able to connect to it and log in using the WEP key.  The problem
> > comes when assigning an IP address through DHCP...sometimes it takes an
> > extremely long time (over a minute) and sometimes no IP address is
> > assigned at all.  If I disconnect and reconnect the NIC to the router
> > (in other words, repeat the process), most of the time I'll get an IP.
> > Sometimes I have to do this 3-4 times before it works.
> >
> > The question I have is...why is this occurring?  Is this (as I suspect)
> > a bad router, since it does work eventually?  Or is this something
> > else?
> >
> > Thanks,
> >
> >
> >
> > Adam
> > http://www.searchenginefriendlylayouts.com/
> >

"SEFL" <a***@searchenginefriendlylayouts.com> wrote in message
news:1157748427.360968.128450@i42g2000cwa.googlegroups.com...
> Hi Jack,
>
> Thanks for clearing that MAC thing up.  I figured that had something to
> do with it since, when I originally hooked up the modem, it was hooked
> up to the same NIC that I cloned the MAC from.
>
> A2.  It doesn't have anything to do with the DHCP.  I'm just pointing
> out that I can at least reach the router and communicate with it.  The
> router simply doesn't assign IPs via DHCP consistently, and that's the
> issue.
>
> Thanks.
>
>
>
>
> Adam
>
>
> Jack (MVP-Networking). wrote:
>> Hi
>>
>> A1.  Without cloning the MAC you cannot go on to your services, it is
>> like
>> the ID and Pas Word.  The few pages that you saw are probably cached on
>> your
>> hard drive a while ago.
>>
>> A2. I do not know what WEP as to do with DHCP and assigning IPs?
>>
>> Try to fix your Network Stacks by doing the follow,
>> http://www.ezlan.net/clean#refreshnet
>>
>> Jack (MVP-Networking).
>>
>>
>> "SEFL" <a***@searchenginefriendlylayouts.com> wrote in message
>> news:1157724899.572217.53160@m73g2000cwd.googlegroups.com...
>> > This is going to sound like a rather strange problem, but here goes:
>> >
>> > I've got a TrendNet TEW-432BRP wireless router and four computers
>> > trying to access it.  Here's the scenario of issues (one of which was
>> > solved, and I have no idea why):
>> >
>> > 1)  When the router was connected, domains would resolve to IP
>> > addresses (e.g. Google.ca to 64.233.161.104) but only a few sites would
>> > be accessible via a web browser.  I "solved" this by cloning the MAC
>> > address of the one machine that was wired into the router.  Why this
>> > worked, I have absolutely no idea, but it did.
>> >
>> > 2) NICs (both wired and wireless) will detect the router/network, and I
>> > am able to connect to it and log in using the WEP key.  The problem
>> > comes when assigning an IP address through DHCP...sometimes it takes an
>> > extremely long time (over a minute) and sometimes no IP address is
>> > assigned at all.  If I disconnect and reconnect the NIC to the router
>> > (in other words, repeat the process), most of the time I'll get an IP.
>> > Sometimes I have to do this 3-4 times before it works.
>> >
>> > The question I have is...why is this occurring?  Is this (as I suspect)
>> > a bad router, since it does work eventually?  Or is this something
>> > else?
>> >
>> > Thanks,
>> >
>> >
>> >
>> > Adam
>> > http://www.searchenginefriendlylayouts.com/
>> >
>

> Hi
> Switch off all security filters, if it does not assign an IP through the
> DHCP,  call support, it might be that some thing is wrong with the Router.
> Jack (MVP-Networking).
>
> "SEFL" <a***@searchenginefriendlylayouts.com> wrote in message
> news:1157748427.360968.128450@i42g2000cwa.googlegroups.com...
> > Hi Jack,
> >
> > Thanks for clearing that MAC thing up.  I figured that had something to
> > do with it since, when I originally hooked up the modem, it was hooked
> > up to the same NIC that I cloned the MAC from.
> >
> > A2.  It doesn't have anything to do with the DHCP.  I'm just pointing
> > out that I can at least reach the router and communicate with it.  The
> > router simply doesn't assign IPs via DHCP consistently, and that's the
> > issue.
> >
> > Thanks.
> >
> >
> >
> >
> > Adam
> >
> >
> > Jack (MVP-Networking). wrote:
> >> Hi
> >>
> >> A1.  Without cloning the MAC you cannot go on to your services, it is
> >> like
> >> the ID and Pas Word.  The few pages that you saw are probably cached on
> >> your
> >> hard drive a while ago.
> >>
> >> A2. I do not know what WEP as to do with DHCP and assigning IPs?
> >>
> >> Try to fix your Network Stacks by doing the follow,
> >> http://www.ezlan.net/clean#refreshnet
> >>
> >> Jack (MVP-Networking).
> >>
> >>
> >> "SEFL" <a***@searchenginefriendlylayouts.com> wrote in message
> >> news:1157724899.572217.53160@m73g2000cwd.googlegroups.com...
> >> > This is going to sound like a rather strange problem, but here goes:
> >> >
> >> > I've got a TrendNet TEW-432BRP wireless router and four computers
> >> > trying to access it.  Here's the scenario of issues (one of which was
> >> > solved, and I have no idea why):
> >> >
> >> > 1)  When the router was connected, domains would resolve to IP
> >> > addresses (e.g. Google.ca to 64.233.161.104) but only a few sites would
> >> > be accessible via a web browser.  I "solved" this by cloning the MAC
> >> > address of the one machine that was wired into the router.  Why this
> >> > worked, I have absolutely no idea, but it did.
> >> >
> >> > 2) NICs (both wired and wireless) will detect the router/network, and I
> >> > am able to connect to it and log in using the WEP key.  The problem
> >> > comes when assigning an IP address through DHCP...sometimes it takes an
> >> > extremely long time (over a minute) and sometimes no IP address is
> >> > assigned at all.  If I disconnect and reconnect the NIC to the router
> >> > (in other words, repeat the process), most of the time I'll get an IP.
> >> > Sometimes I have to do this 3-4 times before it works.
> >> >
> >> > The question I have is...why is this occurring?  Is this (as I suspect)
> >> > a bad router, since it does work eventually?  Or is this something
> >> > else?
> >> >
> >> > Thanks,
> >> >
> >> >
> >> >
> >> > Adam
> >> > http://www.searchenginefriendlylayouts.com/
> >> >
> >