Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] DNS Working but can't connect to anything

From: Martin Visser <martinvisser99@xxxxxxxxx>
Date: Wed, 28 Jan 2009 17:59:33 +1100
Staedlerx,

A couple of things.

1. You are running a fairly old Service Pack version of XP. From what I recall a lot of fixes for network issues were incorporated in SP3  - I would look at upgrading. (I know this is the usual helpdesk answer, but in this case it may work). Even check driver levels - I had a devil of job getting a laptop working with WPA2. (The Windows native wireless config worked, but not the Intel utility).  It wasn't till I upgraded the 2 year old Intel drivers that everything worked swimmingly.

2. Make sure when you test the different interfaces and things go wrong, do the change and also do a reboot. While Windows since W2K should support dynamic updating etc, it ain't always so. (For instance I am running Vista SP1 on one of my machines, and I have found exactly the same issue (following a couple sleep/wake cycles) that DHCP and IP all work, but I can't get a DNS response until a reboot.

As your DNS response is reaching your machine (and being rejected), I am not sure Wireshark can help you. (MS Network Monitor does show the processes that packets are being sent too, but I am not sure whether this will tell you anything new).

Regards, Martin

MartinVisser99@xxxxxxxxx


On Wed, Jan 28, 2009 at 3:30 PM, staedtlerx <staedtlerx@xxxxxxxxx> wrote:
@Hansang - No luck there either
p.s. the "http" is just a result of email transfer
 


 
On Tue, Jan 27, 2009 at 10:51 AM, Hansang Bae <hbae@xxxxxxxxxx> wrote:
staedtlerx wrote:
> FWIW I have NO firewalls running and I get this same behavior in safe
> mode. What's perplexing is how everything works fine with my internal
> wifi but not the 4 other interfaces. Diags below:

> Windows IP Configuration
>
>         Host Name . . . . . . . . . . . . : laptop
>         Primary Dns Suffix  . . . . . . . :
>         Node Type . . . . . . . . . . . . : Hybrid
>         IP Routing Enabled. . . . . . . . : No
>         WINS Proxy Enabled. . . . . . . . : No
>         DNS Suffix Search List. . . . . . : nyc.rr.com <http://nyc.rr.com>
>
> Ethernet adapter Dock LAN:
>
>         Connection-specific DNS Suffix  . : nyc.rr.com <http://nyc.rr.com>
>         Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E
> Gigabit Ethernet Controller
>         Physical Address. . . . . . . . . : 00-1A-80-64-01-30
>         Dhcp Enabled. . . . . . . . . . . : Yes
>         Autoconfiguration Enabled . . . . : Yes


Your DNS suffix looks odd.  What's the http://.... doing there?   But I
do see hybrid for your Node Type.  Try deleting the keys that I
mentioned before.  I'm not sure why your boxes decided to use NBT
(NetBIOS over TCP) for Windows name resolution.


--

Thanks,
Hansang
___________________________________________________________________________
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


___________________________________________________________________________
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