<div>
Try opening a command prompt on a computer experiencing slowness and type ipconfig /flushdns<br />
<br />
Also...verify that the DHCP server is only giving out the ip address of the DNS server for DNS, and not the old one. &nbsp;You will also want to verify in the command prompt the DNS server...by using <br />
ipconfig /all<br />
<br />
If you see the old ip address of the DNS server you took offline anywhere you found your problem. &nbsp;Also flushdns may help otherwise. &nbsp;<br />
<br />
Good luck
</div>


<div>
At first you need to find the cause. Sounds like it could be a DNS problem, like the client tries to reach the old retired DNS and after a few seconds it tries the next one? But really just guessing. An easy network monitoring could be done if you just download wireshark (open source sniffer) install it on an affected workstation and sniff the packets. See what packet was sent last before the &quot;delay&quot; occurs, i would bet on DNS, but maybe its also something completely different like proxy authentification (Guessing here, i dont know what your real network looks like).
</div>


<div>
Thank you for your input,<br />
<br />
No slowness noted on the LAN it is just when surfing the web.<br />
The DNS server was setup correctly
</div>


<div>
just as a test...set the DNS server as a static ip on the network connection tcp/ip settings of one of the computers. &nbsp;It's a no brainer that slow web sites relates to dns. &nbsp;It's worth a try...
</div>


<div>
I did try that. Now it is even slower
</div>


<div>
Hi Kyodai,<br />
<br />
I did install Wireshark, could you please guide me on how to use it?<br />
<br />
Thank you
</div>


<div>
Hi, just open up Wireshark, then click capture -- Interfaces and click the start button on the interface you want to sniff on. You will see every single package that leaves or arrives at the network card. with setting the filters (these are very mighty, the online Help with F1 gives much info here) you can blind out unwanted traffic or look at scefic traffic, like http or DNS. You can click a single package and look at details in the lower window, after some minutes practice you get a feeling to read the packages if you know a little bit about TCP/IP. ALso helpfull stuuf appears when you right click a package. A quite cool tool is &quot;Follow conversation&quot; or the various quick filters you can apply. The column &quot;Time&quot; is in your case very interesting, here you can identify delays! You will need to analyze the conversation a bit. Normally in a local network server responses should be arond several miliseconds, for example in our network a usual response from the DNS server takes around 10 miliseconds and these could be faster! If the proxy servers answer just takes too long the problem would very likely be on the proxy, but in that case ALL clients in the network segment should experience the same problems. Maybe the Proxys primary DNS times out or its some firewall rule or stuff. You need to analyse a bit more here. Usually delays can happen on the proxy when there is a problem with authentication and it uses a fallback, or similar stuff. I hope sniffing the traffic and seeing what really happens when client and proxy talks will give you the solution.
</div>


<div>
I have installed NS Network Monitor 3.2. I was not able to attach the caption file as it says that it is not supported. I did include a part of the caption and it is referring to the 2 old servers that I have retired and seized the roles and the services from.<br />
<br />
8832 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;549.683376 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{DNS:1582, UDP:1581, IPv4:48} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TAHITI &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;P2SERVER &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS:QueryId = 0xC726, QUERY (Standard query), Query &nbsp;for tracking.realtor.com of type Host Addr on class Internet<br />
8833 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;549.730526 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<a href="HTTP:1509" rel="ugc">HTTP:1509</a>, UDP:1508, IPv4:1507} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DALLAS &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;239.255.255.250 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP:Request, NOTIFY * <br />
8834 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;549.730526 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<a href="HTTP:1512" rel="ugc">HTTP:1512</a>, UDP:1511, IPv6:1510} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FE80:0:0:0:5952:58A5:2663:<wbr />C520 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FF02:0:0:0:0:0:0:C &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP:Request, NOTIFY * <br />
8835 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;550.207046 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:2, IPv4:1} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PARIS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for SUN &nbsp;&lt;0x00&gt; Workstation Service<br />
8836 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;550.277270 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:30, IPv4:29} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOGOTA &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for QUEBEC &nbsp; &lt;0x00&gt; Workstation Service<br />
8837 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;550.278273 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:32, IPv4:31} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOGOTA &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for QUEBEC &nbsp; &lt;0x00&gt; Workstation Service<br />
8838 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;550.382606 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{DNS:1580, UDP:1579, IPv4:48} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TAHITI &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;P2SERVER &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS:QueryId = 0x5840, QUERY (Standard query), Query &nbsp;for homestore.122.2o7.net of type Host Addr on class Internet<br />
8839 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;550.580237 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ALEP &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.9 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ARP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ARP:Request, 192.168.200.102 asks for 192.168.200.9<br />
8840 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;550.684569 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{DNS:1582, UDP:1581, IPv4:48} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TAHITI &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;P2SERVER &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS:QueryId = 0xC726, QUERY (Standard query), Query &nbsp;for tracking.realtor.com of type Host Addr on class Internet<br />
8841 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;550.957440 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:2, IPv4:1} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PARIS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for SUN &nbsp;&lt;0x00&gt; Workstation Service<br />
8842 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.040705 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:30, IPv4:29} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOGOTA &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for QUEBEC &nbsp; &lt;0x00&gt; Workstation Service<br />
8843 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.042712 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:32, IPv4:31} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOGOTA &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for QUEBEC &nbsp; &lt;0x00&gt; Workstation Service<br />
8844 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.085849 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;HEIDICOMP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.9 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ARP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ARP:Request, 192.168.200.61 asks for 192.168.200.9<br />
8845 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.090865 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:1516, IPv4:1515} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;HEIDICOMP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for SHOP &nbsp; &lt;0x00&gt; Workstation Service<br />
8846 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.382797 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{DNS:1580, UDP:1579, IPv4:48} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TAHITI &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;P2SERVER &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS:QueryId = 0x5840, QUERY (Standard query), Query &nbsp;for homestore.122.2o7.net of type Host Addr on class Internet<br />
8847 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.684760 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{DNS:1582, UDP:1581, IPv4:48} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TAHITI &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;P2SERVER &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS:QueryId = 0xC726, QUERY (Standard query), Query &nbsp;for tracking.realtor.com of type Host Addr on class Internet<br />
8848 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.687769 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<a href="HTTP:22" rel="ugc">HTTP:22</a>, UDP:21, IPv6:20} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FE80:0:0:0:B510:3C6F:C337:<wbr />E39 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FF02:0:0:0:0:0:0:C &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP:Request, M-SEARCH * <br />
8849 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.688773 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<a href="HTTP:24" rel="ugc">HTTP:24</a>, UDP:23, IPv4:6} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;GREG-T60 &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;239.255.255.250 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP:Request, M-SEARCH * <br />
8850 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.688773 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MOSCOW &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.9 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ARP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ARP:Request, 192.168.200.55 asks for 192.168.200.9<br />
8851 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.690779 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:77, IPv4:76} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MOSCOW &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for MOON &nbsp; &lt;0x20&gt; File Server Service<br />
8852 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.690779 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:77, IPv4:76} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MOSCOW &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for SYDNEY &nbsp; &lt;0x20&gt; File Server Service<br />
8853 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.713853 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:2, IPv4:1} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PARIS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for MASTER &nbsp; &lt;0x00&gt; Workstation Service<br />
8854 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.805144 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:30, IPv4:29} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOGOTA &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for QUEBEC &nbsp; &lt;0x00&gt; Workstation Service<br />
8855 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.807150 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:32, IPv4:31} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOGOTA &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for QUEBEC &nbsp; &lt;0x00&gt; Workstation Service<br />
8856 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;551.835240 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:1516, IPv4:1515} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;HEIDICOMP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for SHOP &nbsp; &lt;0x00&gt; Workstation Service<br />
8857 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.180341 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{SMB:1584, UDP:1583, IPv4:29} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOGOTA &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BROWSER &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BROWSER:Host Announcement, ServerName = BOGOTA<br />
8858 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.182347 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{SMB:1586, UDP:1585, IPv4:31} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOGOTA &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BROWSER &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BROWSER:Host Announcement, ServerName = BOGOTA<br />
8859 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.263606 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<a href="HTTP:1509" rel="ugc">HTTP:1509</a>, UDP:1508, IPv4:1507} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DALLAS &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;239.255.255.250 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP:Request, NOTIFY * <br />
8860 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.263606 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<a href="HTTP:1512" rel="ugc">HTTP:1512</a>, UDP:1511, IPv6:1510} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FE80:0:0:0:5952:58A5:2663:<wbr />C520 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FF02:0:0:0:0:0:0:C &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP:Request, NOTIFY * <br />
8861 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.309753 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<a href="HTTP:1509" rel="ugc">HTTP:1509</a>, UDP:1508, IPv4:1507} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DALLAS &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;239.255.255.250 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP:Request, NOTIFY * <br />
8862 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.309753 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{<a href="HTTP:1512" rel="ugc">HTTP:1512</a>, UDP:1511, IPv6:1510} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FE80:0:0:0:5952:58A5:2663:<wbr />C520 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FF02:0:0:0:0:0:0:C &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SSDP:Request, NOTIFY * <br />
8863 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.418099 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:77, IPv4:76} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MOSCOW &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for MOON &nbsp; &lt;0x20&gt; File Server Service<br />
8864 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.418099 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:77, IPv4:76} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MOSCOW &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for SYDNEY &nbsp; &lt;0x20&gt; File Server Service<br />
8865 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;552.446189 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{UDP:2, IPv4:1} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PARIS &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;192.168.200.255 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NbtNs:Query Request for MASTER &nbsp; &lt;0x00&gt; Workstation Service<br />

</div>


<div>
Well then it is very likely that these 2 old servers are still in some local settings. The Client still has these somewhere in the settings. Unfortunately you did not note which of the servers are the retired ones, but i would look up the retired server names in the client settings and remove them. In large companies you probably distribute settings centralized, so you would need to remove them from your windows policies or DHCP or similar setting distributing services.
</div>


<div>
The servers names are Moon and Sun and we have a small network wit 1 DC and a Citrix server<br />
WE have a T1 connection with a Cisco Router managed by AT&amp;T is there any seeing on the router where to enter the DC's names and IP addresses?
</div>


<div>
I need help on DNS forwarders.<br />
Can someone help me on setting my &nbsp; ISPs DNS servers as forwarders
</div>


<div>
&quot;It's a no brainer that slow web sites relates to dns.&quot;<br />
<br />
C'mon...who was right? &nbsp;:)<br />
<br />
Glad you fixed it
</div>


<div>
<div class="content wysiwyg-content">
Recently we started experiencing slowliness in surfing the web.<br />
The only changes we have had is we used to have two DC's (2000 and 2003) something went wrong with the 2000 server (used to be DNS and DHCP server), so we have retired it and we now using only the 2003 server after seizing the roles and moving the services to the 2003 server.<br />
<br />
On an other note, I have been asked to install Network Monitor on a client machine and take a network trace when the problem occurs. And I need help on that.<br />
<br />
P;lease advise.<br />
<br />
Thank u
</div>
</div>


Recently we started experiencing slowliness in surfing the web.
The only changes we have had is we used to have two DC's (2000 and 2003) something went wrong with the 2000 server (used to be DNS and DHCP server), so we have retired it and we now using only the 2003 server after seizing the roles and moving the services to the 2003 server.

On an other note, I have been asked to install Network Monitor on a client machine and take a network trace when the problem occurs. And I need help on that.

P;lease advise.

Thank u

Experiencing slowliness in surfing the Web and in printing

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.