can't UNC to server

Not sure if I'm in the right spot, but maybe someone can re-direct me to the
right place to post this thread.

We recently setup a new network for a company we consult for and I'm not
sure why this error is occuring. I'm logged in as domain admin. and can't
UNC to the c$ share of another server on the network. It could be a dns
issue, but I don't see the problem and have configured dns similar to other
networks. When I try from server A to get to server B I get "the network
name does not exist" and when I try from Server B to Server A I get a long
delay before getting an error. No firewall is configured on the servers.

The reason I need this to work is that I am using backup-exec and it uses
unc shares to backup documents to itself. It is not a backup exec problem as
the error happens when I try to do it outside of backup-exec. I also need to
xcopy files in certain situations and I believe it is causing problems. I
will follow with more details, but I just wanted to get the original thread
started. I can see the c$ share (which is default for server 2003) in
computer management- shares.

From Server A I can ping netbios name and dns resolves full machine dns name
and pings the IP of server B
From Server A I try to do start>run> \\servername\c$ and get "the specified
network name is no longer available"
and \\servername.domainname.local\c$ and I get "no network provider accepted
the given network path" I can UNC to \\IP_of_serverB\c$ to see the files.

From server b I can ping server A by machine name and it resolves to
servername.domain.local and the IP address of that machine.
From Server B when I do \\serverA\c$ it takes about 5 minutes longer than it
should take and then displays the file structure.


I have tried to disjoin and rejoin server A to the domain and it did not help.

It could be master browser issue. Try to use borwstat to check the status.
Or this search result may help too.

specified network name is not longer availableSystem error 64 - The
specified network name is no longer available. System error 53. The network
path was not found. Event ID 3013 - Description: The ...
http://www.chicagotech.net/troublesh...temerror64.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"themoelman" <(E-Mail Removed)> wrote in message
news:95680519-E419-49EA-BFF5-(E-Mail Removed)...
> Not sure if I'm in the right spot, but maybe someone can re-direct me to
> the
> right place to post this thread.
>
> We recently setup a new network for a company we consult for and I'm not
> sure why this error is occuring. I'm logged in as domain admin. and can't
> UNC to the c$ share of another server on the network. It could be a dns
> issue, but I don't see the problem and have configured dns similar to
> other
> networks. When I try from server A to get to server B I get "the network
> name does not exist" and when I try from Server B to Server A I get a long
> delay before getting an error. No firewall is configured on the servers.
>
> The reason I need this to work is that I am using backup-exec and it uses
> unc shares to backup documents to itself. It is not a backup exec problem
> as
> the error happens when I try to do it outside of backup-exec. I also need
> to
> xcopy files in certain situations and I believe it is causing problems. I
> will follow with more details, but I just wanted to get the original
> thread
> started. I can see the c$ share (which is default for server 2003) in
> computer management- shares.
>
> From Server A I can ping netbios name and dns resolves full machine dns
> name
> and pings the IP of server B
> From Server A I try to do start>run> \\servername\c$ and get "the
> specified
> network name is no longer available"
> and \\servername.domainname.local\c$ and I get "no network provider
> accepted
> the given network path" I can UNC to \\IP_of_serverB\c$ to see the files.
>
> From server b I can ping server A by machine name and it resolves to
> servername.domain.local and the IP address of that machine.
> From Server B when I do \\serverA\c$ it takes about 5 minutes longer than
> it
> should take and then displays the file structure.
>
>
> I have tried to disjoin and rejoin server A to the domain and it did not
> help.
>
>

did browstat status and got results.

browsing is active, master browser name, backup servers retrieved from
master (there were only 3 here, the pdc, the msx server, and the backup
server)

it listed how many "servers" in the domain
and listed there are 1 domains in domain [domainname] on transport

does that look normal?

"Robert L. (MS-MVP)" wrote:

> It could be master browser issue. Try to use borwstat to check the status.
> Or this search result may help too.
>
> specified network name is not longer availableSystem error 64 - The
> specified network name is no longer available. System error 53. The network
> path was not found. Event ID 3013 - Description: The ...
> http://www.chicagotech.net/troublesh...temerror64.htm
>
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
>
>
> "themoelman" <(E-Mail Removed)> wrote in message
> news:95680519-E419-49EA-BFF5-(E-Mail Removed)...
> > Not sure if I'm in the right spot, but maybe someone can re-direct me to
> > the
> > right place to post this thread.
> >
> > We recently setup a new network for a company we consult for and I'm not
> > sure why this error is occuring. I'm logged in as domain admin. and can't
> > UNC to the c$ share of another server on the network. It could be a dns
> > issue, but I don't see the problem and have configured dns similar to
> > other
> > networks. When I try from server A to get to server B I get "the network
> > name does not exist" and when I try from Server B to Server A I get a long
> > delay before getting an error. No firewall is configured on the servers.
> >
> > The reason I need this to work is that I am using backup-exec and it uses
> > unc shares to backup documents to itself. It is not a backup exec problem
> > as
> > the error happens when I try to do it outside of backup-exec. I also need
> > to
> > xcopy files in certain situations and I believe it is causing problems. I
> > will follow with more details, but I just wanted to get the original
> > thread
> > started. I can see the c$ share (which is default for server 2003) in
> > computer management- shares.
> >
> > From Server A I can ping netbios name and dns resolves full machine dns
> > name
> > and pings the IP of server B
> > From Server A I try to do start>run> \\servername\c$ and get "the
> > specified
> > network name is no longer available"
> > and \\servername.domainname.local\c$ and I get "no network provider
> > accepted
> > the given network path" I can UNC to \\IP_of_serverB\c$ to see the files.
> >
> > From server b I can ping server A by machine name and it resolves to
> > servername.domain.local and the IP address of that machine.
> > From Server B when I do \\serverA\c$ it takes about 5 minutes longer than
> > it
> > should take and then displays the file structure.
> >
> >
> > I have tried to disjoin and rejoin server A to the domain and it did not
> > help.
> >
> >
>
>

I too have been tearing my hair out with a similar issue (please do post if
you find a solution!)

One thing I did come across along my trials was that although you may not
think it, Backup Exec can cause issues as it installs a network filter of
some sort. It recommends installing a hot fix available from Symantec.
Although it didn't solve my particular problem, I hope it does yours.

David.

can you see the shares using netview command?


--
dennyd
------------------------------------------------------------------------
dennyd's Profile: http://forums.techarena.in/member.php?userid=50495
View this thread: http://forums.techarena.in/showthread.php?t=908765

http://forums.techarena.in

My team fixed it when I was on vacation - VMWare server installs sometimes
wreck the tcp/ip stack and need a winsock fix done to them. It solved the
problems we had. Hope it helps.

"coolvid" wrote:

> I too have been tearing my hair out with a similar issue (please do post if
> you find a solution!)
>
> One thing I did come across along my trials was that although you may not
> think it, Backup Exec can cause issues as it installs a network filter of
> some sort. It recommends installing a hot fix available from Symantec.
> Although it didn't solve my particular problem, I hope it does yours.
>
> David.