[Martin Visser <martinvisser99@xxxxxxxxx>]

irfan and ionannis,

You guys obviously are not following the mail thread or reading the results. This is not a "basic networking issue" that has been highlighted. The fact that the captures show results back from the router indicates that DNS and internet connectivity is working. The problem here is that the client is rejecting the DNS response (hence the ICMP port unreachable message). So we are not looking for a network connectivity problem as much as a operating system level issue as to why a perfectly valid DNS response is being rejected.

Regards, Martin

MartinVisser99@xxxxxxxxx

On Wed, Jan 28, 2009 at 5:22 PM, <irfan.sanober@xxxxxxxxxxxxxxxxx> wrote:

Step 1:
At command prompt
ping 4.2.2.2
if successful goto next step otherwise run
tracert 4.2.2.2          (and post your result)

Step 2:
nslookup www.yahoo.com
if successfully resolved goto next step otherwise Change your DNS to Service provider DNS or universal dns like 2.4.4.4

Step 3:
ping www.yahoo.com
if successful go to next step, otherwise try to connect internet with different method like Dialup or via some friend wifi internet connectivity.

Step 4:
try to browse www.yahoo.com form your internet explorer
if not successful install some other internet browser like firefox.

please let us know your Findings...

Hope thats help

Thanks & Regards

Mirza Irfan Sanober

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe