Strange Entries in MS Network Monitor - debugging slow sql connect

Hello All,
I am trying to debug a machine that is very slow to connect to sql servers
in our organisation. It's slow connecting to all. I have run MS Network
monitor 3 and have seen some strange entries appear when I try to
connect....


192.168.0.132 192.168.0.2 NbtNs NbtNs: Query
Request for WPAD.NET.AU.

Any ideas what these mean and why they are generated??? I have also seen
"DHCP Boot Request" turn up when trying to open sql connection that fails.
Any ideas what these events may actually be? They are both from the address
of the machine in question "192.168.0.2"

Network is TCP/IP windows xp machines on a lan, with internet supplied
through ISA Server on win2k server box.

Thanks in advance - any ideas would be appreciated - Ed.
3 0.000000



a








Ed

"Ed" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> in our organisation. It's slow connecting to all. I have run MS Network
> monitor 3 and have seen some strange entries appear when I try to

Everything seen in a packet sniffer is strange.
Heck, spending too much time looking at one probably causes cancer in lab
animals.

> 192.168.0.132 192.168.0.2 NbtNs NbtNs: Query
> Request for WPAD.NET.AU.

It is for Proxy Server Auto-detection.
http://www.microsoft.com/technet/isa...discovery.mspx

> "DHCP Boot Request" turn up when trying to open sql connection that fails. Any
> ideas what these events may actually be? They are both from the address

Probably related to machines that look for DHCP to "network boot" as one of
their boot options.

Nothing here is related (IMO). I really doubt you are going to see anything in
packet sniffing that makes the machine slow.

Machines don't connect to SQL Servers,...Applications do. The problem is
probably in the Application, or ODBC, or the SQL Server Service itself. The
"query" either goes from the App to the SQL Service, or it doesn't,....the SQL
Service either responds to the "query" right away,..or it doesn't. It is not a
"network thing" unless the amount of data returned is so large it overwhelms the
network infrastructure, but I really really really doubt that. Such a huge
amount of data may overwhelm the SQL Service itself first before it ever bothers
the network, which would cause the SQL Service to simply not respond or take a
really really long time.

Just my 2 cents....

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------