specified network name is no longer available

We're getting the error 'specified network name is no
longer available' copying files to our new Windows 2003
file server. There is no additional software installed on
the server. The error doesn't always occur, just often
enough to be a problem.

I suspect the hotfix from Microsoft Knowledge Base
Article - 821464 might be the solution, but there's no
link to download it. Also, this KB artical is not for
Windows Server 2003 I am not using any of the products
mentioned in this KB that install a conflicting filter
driver.

Any suggestiongs?

Thanks,

Dean

Hi,

Are you using the actual server name, or an alias name when connecting to
the server?

If you are using an Alias name (CNAME record in DNS), then you may need to
disable strict name checking on the server using
http://support.microsoft.com/default...B;EN-US;281308 (the hotfix
is not needed on Windows 2003)



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.

Matthew,

I'm using the actual server name (in this case 'data'). I've also tried
using the IP address. We are on an NT4 Domain if it makes any difference.
I've got 'data' in the hosts file of the connecting server too.

Dean

"Matthew [MSFT]" <(E-Mail Removed)> wrote in message
news:2xt%(E-Mail Removed)...
> Hi,
>
> Are you using the actual server name, or an alias name when connecting to
> the server?
>
> If you are using an Alias name (CNAME record in DNS), then you may need to
> disable strict name checking on the server using
> http://support.microsoft.com/default...B;EN-US;281308 (the hotfix
> is not needed on Windows 2003)
>
>
>
> 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.
>
>

Hi Dean,

If the connection fails using the IP address as well then I would tned to
think name resolution will not be the issue. If it is sporatic and from
all clients, then I would suggest looking at the NIC properties. I would
set the duplex and speed specific to the network (ie. 100 MBps full
duplex). You may also want to check the port where the server is plugged
into, maybe change ports or try a different piece of hardware. Using a
different NIC in the server may also be worth trying.

You may also look into security settings on the server. However, if this
was an issue, I would think the issue would be consistant.


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.

It appears we are having the same issue in regards to
moving large files, 1 GB+. We are running Windows 2003
Std and Windows 2003 Appliance edition. After an
unspecified amount of time the file copy the file copy
errors out with network resource is no longer available.
We can not tie this error to any type of network outage.
We have the particualr servers setup with static WINS
entries and both have proper DNS entries. The one server
has 2 active NIC's in it one going to an internal public
network and the other goes to an internal private
network. The other server has 2 NIC's only one is
enabled. Both of these are HP/Compaq servers. We have
tried switching port speed and duplex, and also have
switched to different cables and different ports in the
switch. The only thing that I do notice is that while
the copy is in porgress both NIC's appear to be maxed for
network utilization which makes the server seem
unresponsive through RDC. But on the other we have been
getting this when with low network utilization as well on
the 2 NIC server. Any other ideas?


>-----Original Message-----
>Hi Dean,
>
>If the connection fails using the IP address as well
then I would tned to
>think name resolution will not be the issue. If it is
sporatic and from
>all clients, then I would suggest looking at the NIC
properties. I would
>set the duplex and speed specific to the network (ie.
100 MBps full
>duplex). You may also want to check the port where the
server is plugged
>into, maybe change ports or try a different piece of
hardware. Using a
>different NIC in the server may also be worth trying.
>
>You may also look into security settings on the server.
However, if this
>was an issue, I would think the issue would be
consistant.
>
>
>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.
>
>
>.
>

After moving ports around and changing ports away from Auto settings I
finally ended up putting the two machines on one Cisco switch (seperate
VLANS). So the traffic leaves the switch, goes through a PIX firewall and
then re-enters the switch to the other vlan. Could this be the issue?
Surely a copy should work accross the PIX?

Dean


"Ken" <(E-Mail Removed)> wrote in message
news:18b3501c420ce$381f8c80$(E-Mail Removed)...
> It appears we are having the same issue in regards to
> moving large files, 1 GB+. We are running Windows 2003
> Std and Windows 2003 Appliance edition. After an
> unspecified amount of time the file copy the file copy
> errors out with network resource is no longer available.
> We can not tie this error to any type of network outage.
> We have the particualr servers setup with static WINS
> entries and both have proper DNS entries. The one server
> has 2 active NIC's in it one going to an internal public
> network and the other goes to an internal private
> network. The other server has 2 NIC's only one is
> enabled. Both of these are HP/Compaq servers. We have
> tried switching port speed and duplex, and also have
> switched to different cables and different ports in the
> switch. The only thing that I do notice is that while
> the copy is in porgress both NIC's appear to be maxed for
> network utilization which makes the server seem
> unresponsive through RDC. But on the other we have been
> getting this when with low network utilization as well on
> the 2 NIC server. Any other ideas?
>
>
> >-----Original Message-----
> >Hi Dean,
> >
> >If the connection fails using the IP address as well
> then I would tned to
> >think name resolution will not be the issue. If it is
> sporatic and from
> >all clients, then I would suggest looking at the NIC
> properties. I would
> >set the duplex and speed specific to the network (ie.
> 100 MBps full
> >duplex). You may also want to check the port where the
> server is plugged
> >into, maybe change ports or try a different piece of
> hardware. Using a
> >different NIC in the server may also be worth trying.
> >
> >You may also look into security settings on the server.
> However, if this
> >was an issue, I would think the issue would be
> consistant.
> >
> >
> >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.
> >
> >
> >.
> >

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.