|
Back in the saddle again
Join Date: Oct 2001
Location: Central TX west of Houston
Posts: 57,101
|
Well, if you can ping the local router, but not anything past the router, normally, I'd say that the default gateway isn't configured.
Can you do a traceroute to 4.2.2.2 and provide the results?
If connectivity to local devices is working, then it's just ARP working. To get past your default gateway, the Solaris host needs a default gateway, you already have that. The next thing that needs to happen is that the default gateway will probably be translating (NAT) the 192.168.1.104 address to whatever it's outside address is (assigned by the ISP). If the .104 address isn't translated, then nothing past your router will know where to send the packet to get it back to the Solaris box. Actually, chances are the ISP will block the traffic before it goes anywhere.
If the XP box is working fine then it would seem that the NAT is working ok.
Show us the results of the trace route.
I did once see an issue a long time ago where a specific type of traffic was failing from a UNIX box. The guy swore that it was the router blocking the traffic, but at some point we realized that the TTL of the packets for that traffic had been set to 1 which kept all of the traffic local. Seems highly unlikely to be the problem in this case.
Try setting the address to something different 192.168.1.10 or .200 or .74, whatever.
__________________
Steve
'08 Boxster RS60 Spyder #0099/1960
- never named a car before, but this is Charlotte.
'88 targa  SOLD 2004 - gone but not forgotten
|