Conflict with D-Link wireless and Intel wired PC cards

I have a Fujitsu 550 Lifebook laptop, that has been running with an Intel
EtherExpress Pro 10/100 ethernet PC Card.

I just added a D-Link AirPlus DWL-650+ 802.11b card, and installed the
D-Link DI-614+ wireless router.

When both cards are installed, I cannot ping the router or access the
internet. This sounds like a hardware problem, BUT the wireless card
utility reports good connectivity, and can see the wireless router, and I
can use winipcfg to release and renew the IP address for the wireless card.
I interpret this to mean that the hardware is working properly and there is
some wierd problem with the tcp/ip setup.

The wired card is set up with a defined ip address.
I tried the wireless card with both defined and dhcp assigned address.
OS is Win98

The router has been changed from the default private LAN 198.168.0.1 to
198.168.168.1, but that should not matter. Subnet mask is 255.255.255.0 in
all cases. WEP is currently turned off.

I tried setting up hardware profiles in Device Manager for wired and
wireless, with one card disabled in each. This seems to work, but there
should be no reason I can see why both should not work.

Any suggestions?

Peter

"Peter Harrison" <(E-Mail Removed)> wrote in message
news:bg6itb$fuq$(E-Mail Removed)...
> I have a Fujitsu 550 Lifebook laptop, that has been running with an Intel
> EtherExpress Pro 10/100 ethernet PC Card.
>
> I just added a D-Link AirPlus DWL-650+ 802.11b card, and installed the
> D-Link DI-614+ wireless router.
>
> When both cards are installed, I cannot ping the router or access the
> internet. This sounds like a hardware problem, BUT the wireless card
> utility reports good connectivity, and can see the wireless router, and I
> can use winipcfg to release and renew the IP address for the wireless
card.
> I interpret this to mean that the hardware is working properly and there
is
> some wierd problem with the tcp/ip setup.
>
> The wired card is set up with a defined ip address.
> I tried the wireless card with both defined and dhcp assigned address.
> OS is Win98
>
> The router has been changed from the default private LAN 198.168.0.1 to
> 198.168.168.1, but that should not matter. Subnet mask is 255.255.255.0
in
> all cases. WEP is currently turned off.
>
> I tried setting up hardware profiles in Device Manager for wired and
> wireless, with one card disabled in each. This seems to work, but there
> should be no reason I can see why both should not work.
>
Try http://support.microsoft.com/default...b;en-us;327947

-KENT

Some of the D-Link units have a proprietary high-speed mode. Its called
either 2X or 4X. Try turning that off.

"Kent Smith" <(E-Mail Removed)> wrote in message
news:bgce9p$10t1$(E-Mail Removed)...
>
> "Peter Harrison" <(E-Mail Removed)> wrote in message
> news:bg6itb$fuq$(E-Mail Removed)...
> > I have a Fujitsu 550 Lifebook laptop, that has been running with an
Intel
> > EtherExpress Pro 10/100 ethernet PC Card.
> >
> > I just added a D-Link AirPlus DWL-650+ 802.11b card, and installed the
> > D-Link DI-614+ wireless router.
> >
> > When both cards are installed, I cannot ping the router or access the
> > internet. This sounds like a hardware problem, BUT the wireless card
> > utility reports good connectivity, and can see the wireless router, and
I
> > can use winipcfg to release and renew the IP address for the wireless
> card.
> > I interpret this to mean that the hardware is working properly and there
> is
> > some wierd problem with the tcp/ip setup.
> >
> > The wired card is set up with a defined ip address.
> > I tried the wireless card with both defined and dhcp assigned address.
> > OS is Win98
> >
> > The router has been changed from the default private LAN 198.168.0.1 to
> > 198.168.168.1, but that should not matter. Subnet mask is 255.255.255.0
> in
> > all cases. WEP is currently turned off.
> >
> > I tried setting up hardware profiles in Device Manager for wired and
> > wireless, with one card disabled in each. This seems to work, but there
> > should be no reason I can see why both should not work.
> >
> Try http://support.microsoft.com/default...b;en-us;327947
>
> -KENT
>
>