Re: specified network name is no longer available

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Matthew [MSFT] (mfresoli_at_online.microsoft.com)
Date: 04/13/04 

Date: Tue, 13 Apr 2004 15:29:41 GMT

Hi Dean,

A copy should work thru the PIX, but there is always a possibility packets
could be dropped. The best way to test this would to be place the client
and server on a hub together and see if the issue still occurs. Another
step I can suggest would be to take a network trace from both the client
and server and compare the traffic to see what packets are sent and
received on each end. Network monitor can be used on the server end, and
netcap is a command line utility that can be used on the client (part of
the support tools on XP CD. compatible with 2K clients.) You will need to
view the client capture using network monitor on the server.

Thank you,
Matthew Fresoli
Microsoft Network Support 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights. 
Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm 
Note:  For the benefit of the community-at-large, all responses to this 
message are best directed to the newsgroup/thread from which they 
originated.

Relevant Pages

  • Re: Diagnose co-location networking problem
    ... it was from the client. ... Actually there's significant indication of lost packets and clues that ... 540 retransmit timeouts ... are you using any packetfiltering on the server? ...
    (freebsd-net)
  • Re: process stuck in nfsfsync state
    ... >> server is wedged, not the client. ... Comparing the client and server traces, it looks like fragments in the ... loss for individual packets adds up. ...
    (freebsd-stable)
  • Re: TDS vs. TCP
    ... I start capturing the network traffic between SQL ... Server and the client. ... I don't see any TDS packets but the communication between SQL ... stand-a-lone server and the client, ...
    (microsoft.public.sqlserver.clustering)
  • Re: DHCP
    ... DHCPINFORM is used only if the client has ... >>> I would run ethereal on the server and catch all the packets exchanged ... >>> between the client and server. ... > implies that the host has a "working" IP address. ...
    (comp.os.linux.networking)
  • Re: "Listen on" semantics
    ... the worst thing may well be a screwed-up clock (and ... of packets that were crafted on purpose by malicious minds. ... server then you have a bigger problem since ntpd is not designed to work ... What I want is not so much two copies of ntpd as a separation between client and server functionality. ...
    (comp.protocols.time.ntp)