DSL router assigns DHCP IP, but can't ping router (winxp appears not to listen for packets after getting IP)

Austin, I'm not sure I'm following you fully,
but here is a possible solution.  It seems that
your XP box is unable to update it's arp table
properly- so why not just use static arp entries:

C:\> arp -s 10.10.10.10   00-aa-bb-cc-dd-ee

You may need to do something similar on the router
if it is not showing proper information... Again,
try to set static routes/ARP entries if possible.
Perhaps this will fix your situation...

It's seems strange that your ME box works when the
sniffer is running. It makes me think that somehow
the arp replies are not being sent to the proper MAC
address and the reason it works with the sniffer
active is because the card goes into promiscuous mode
and accepts the improperly addressed packet anyway...

Hope that fixes it,

Steve

Is the bridge enabled on the XP box?
try disabling/deleting it
http://resnet.bgsu.edu/resource/PDFs/Windows%20XP%20Network%20Bridge%20Problem.pdf
http://www.lpt.com/windowsnetworking/regusers/wxpbrdge.htm

This is a fresh install. I've tried both DHCP and static IP on the intel box, niether respond to ping, but with the DHCP method atleast I can see the interface receiving a minimal amount of packets to establish it's IP.

I manually updated the arp table with all 3 MAC adds for the router, the xp and the sun box... no more ARP requests, but still no responding to pings.

This Intel box has a single interface and no bridges can be added or found.


I can ping localhost 10.10.10.82, but that's where it stops... no router no sun box ...I see the outbound requests, but the interface status for 'recieved' doesn't increment.

route print shows interfaces:
0x1 ..................... MS TCP Loopback interface
0x10003 ...[correct MAC]... 3com Etherlink XL 10/100 PCI

active routes:
dest            netmask         gateway      interface  met
0.0.0.0         0.0.0.0         10.10.10.10  10.10.10.82 1
10.10.10.0      255.255.255.0   10.10.10.82  10.10.10.82 20
10.10.10.82     255.255.255.255 127.0.0.1    127.0.0.1   20
10.255.255.255  255.255.255.255 10.10.10.82  10.10.10.82 20
127.0.0.0       255.0.0.0       127.0.0.1    127.0.0.1   1
224.0.0.0       240.0.0.0       10.10.10.82  10.10.10.82 20
255.255.255.255 255.255.255.255 10.10.10.82  10.10.10.82 1
default gateway: 10.10.10.10

I tried setting the DNS to the verizon suggestted, but it doesn't seem to be making it that far along... I don't see anything different over the wire.

This is what I see now, when pinging XP from Sun:
unknown -> (broadcast)  ARP C Who is 10.10.10.82, 10.10.10.82 ?
 10.10.10.82 -> unknown      ARP R 10.10.10.82, 10.10.10.82 is 0:50:4:69:a8:e1
     unknown -> 10.10.10.82  ICMP Echo request (ID: 567 Sequence number: 0)
     unknown -> 10.10.10.82  ICMP Echo request (ID: 567 Sequence number: 1)

...and so on the seq # increases until killed

I see nothing coming out of the XP when pinging the router now? but it still 'request timed out'

and ping from XP to Sun, shows:
10.10.10.82 -> (broadcast)  ARP C Who is 10.10.10.93, unknown ?
     unknown -> 10.10.10.82  ARP R 10.10.10.93, unknown is 8:0:20:b6:1d:c0
repeating ...

any suggestions?

little more... I added the Sun box to the XP arp table and now I see this over the line:

10.10.10.82 -> unknown      ICMP Echo request (ID: 512 Sequence number: 9216)
     unknown -> 10.10.10.82  ICMP Echo reply (ID: 512 Sequence number: 9216)
 10.10.10.82 -> unknown      ICMP Echo request (ID: 512 Sequence number: 9472)
     unknown -> 10.10.10.82  ICMP Echo reply (ID: 512 Sequence number: 9472)

However, the XP box states "request timed out" and the status of the interface for received does not change.

???

Hmmm, the NIC works fine in ME and Linux
check the drivers for the NIC
also try forcing the NIC to 10mbit, half duplex (for troubleshooting)

> would just use the workaround that works for Win_ME
why are you using a work a round?

Because right after a new default DHCP install, even win_me can't ping router, unless the sniffer app is running.


I tried the 10 MB half (no luck)

I give up, windows XP is just use-less, I'll just go back to win_98SE, atleast that works.

Thanks anyway ...

>Because right after a new default DHCP install, even win_me can't ping router
then there is an underlying problem (get the latest greatest drivers for the NIC
what make and model?

Because right after a new default DHCP install, even win_me can't ping router, unless the sniffer app is running.


I tried the 10 MB half (no luck)

I give up, windows XP is just use-less, I'll just go back to win_98SE, atleast that works.

Thanks anyway ...

3com Etherlink XL 10/100 PCI TX NIC (3C905B-TX)

I think it's just that this router sucks and I should have spent the extra 20 bucks for the LinkSYS.

I'll give the Steven the 75 points, since he was the most helpful.

This has gone on long enough, I'll have to borrow a Linksys router from someone at work to really be sure and who knows WHEN I'll get around to that.

Everybody, thanks for your time.

Thanks for the help ... later

Thanks, and good luck to you!
Steve