"Tom A" <(E-Mail Removed)> wrote in message
news:w4USb.16046$(E-Mail Removed) et...
> Hi Guy;
> Sounds like a firewall problem. Check to make sure that XP's built in
> firewall is disabled.
I don't think so. Firewall and filtering is disabled on both PC as portable,
and sniffing the network tells me the ping packets are sent out of the XP
machine, onto the ethernet segment,
but they don't appear on the wireless network.
~G
> HTH;
> TomA
> "Guy Duchatelet" <(E-Mail Removed)> wrote in message
> news:OYTSb.29366$(E-Mail Removed)...
> > Hello,
> > I'm experiencing an annoying problem with my DI-614+
> >
> > a. The Setup:
> > - DI-614+, connected via Cable modem to the Internet - pretty standard
> > config, no filtering or firewalling features enabled
> > - 1 desktop PC, ethernet, connected via LAN port to DI-614+, Windows XP
> > - 1 portable, US Robotics wireless card, Windows 2000
> > On neither of the clients, any TCP/IP filtering nor firewallings is
> > configured.
> >
> > b .The problem:
> > Connecting from both machines to the internet is works like a charm.
> > However connectivity between the desktop on the ethernet segment and the
> > portable
> > on the WiFi segment does not work (and consequently no file or
> > printersharing which I need).
> >
> > c. Tests performed
> > Ping PC-> router : ok
> > Ping Laptop->PC: ok
> > Ping PC-> Laptop, or Laptop->PC: not ok
> > Doing ping tests, I noticed that desktop and portable were able to
resolve
> > each others MAC addresses.
> >
> > I then did some sniffs with Ethereal on both machines while doing pings
> from
> > both ways
> > This is what I found:
> > - ARP requests and response always go through, in both ways. This
includes
> > both the broadcast 'Who has' request,
> > as the unicast response. This confirms that link level connectivity
should
> > be ok, both for broadcast as for unicasts.
> > - The ping icmp echo request is seen in the sniff on the originator of
the
> > request, but is not seen in the sniff on the other end.
> > The same is true for other type of traffic (e.g. TCP port 80
> connections).
> > The behaviour is exactly the same in both directions.
> >
> > So, where are the ip packets going and who is doing it ?
> > I checked whether the MAC addresses of the pings source and destination
> were
> > correct,
> > and normally, the router shouldn't even interfere with that packet, just
> > pump it over, like it did for the ARP packets,
> > which had identical sources and destinations.
> > I redid all these tests starting from a blank configuration (following
the
> > wizard, just configurating my WAN settings), so the config
> > has no filtering enabled at all. The private network is the default
> > 192.168.0.0/24 network.
> > Searched the D-link support site, googled around, but found nothing..
> >
> > Any help or suggestions would be greatly appreciated.
> >
> > BRs,
> > Guy Duchatelet
> >
> >
>
>
|