Re: The specified network name is nolonger available

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Steven L Umbach (sumbach_at_nospam-ameritech.net)
Date: 03/02/04 

Date: Tue, 02 Mar 2004 15:08:45 GMT

OK. From your original post I assumed a larger network because you indicated
a "router" between the computers. From what you describe you have a small
network of a few computers on the same subnet connecting to the internet
through a NAT/router - big difference. Broadcasting should work fine for a
few computers on the same network. I would run ipconfig /all at the command
prompt on all your computers to make sure they are on the same
network/subnet mask. The first three octets of the IP address should be the
same assuming a class c network with the same subnet mask such as
xxx.xxx.xxx.123 where the 123 would be unique on each computer [but not 0 or
255 and the defult gateway is usually 1]. My network for example is
192.168.1.xxx with a 255.255.255.0 subnet mask. Wins will not be needed and
does require a server.

Verify that netbios over tcp/ip is enabled on all computer in tcp/ip
properties/advanced/wins. Use only one network protocol on all computers -
tcp/ip and remove netbeui if found and that the workgroup names are the same
and that the computer names are unique and less than 16 characters. I would
also run netdiag on all the computers looking for any failed tests that may
give a clue. Netdiag is located in the install cd under the support/tools
folder where you will need to run the setup program there to install them.
Also check Event Viewer on all your computers looking for any pertinent
errors, especially ones that report an issue with the "master browser".
Check your lmhosts file to make sure there are no bad entries in it for
computers on your lan. The browse list in My Network Places does not update
immediately and can take over an hour to be correct [searching for the
computer may help as will deleting old shares displayed if possible], so
give it some time especially if computers are started and shut down
frequently and always shut down a computer correctly and not just hit the
power switch. It is also possible you have a flaky network card that may
need to be replaced and check the properties on your network adapters to
make sure they are set at a common network speed such as 100 instead of
using auto. Browsing issues can be tough to track down as it is a "behind
the scenes" operation and in a workgroup the master browser can change
often. Often creating a network shortcut or mapping a drive is a better
option, possibly using static IP addresses on your computers and using the
IP address in the shortcut/mapping. --- Steve

<aa> wrote in message news:OHmrbPDAEHA.1844@TK2MSFTNGP11.phx.gbl...
> Thanks, Steven
> I will look at those Microsoft resources. Meanwhile:
>
> 1. "My guess [not knowing much about your setup] is that you have a
netbios
> name resolution problem"
>
> What details of my setup you need to turn the guess into a fact?
>
> 2. "Broadcasting can be unreliable and should be used only in the
smallest
> networks".
>
> I have THE SMALLIEST network of w2kPro - router - w2kPro (both w2k are on
> the same subnet. Router is used instead of a switch to get Internet
> connection).
> Earlier I had DHCP enabled with the same problem "name nolonger
available".
> Now to eliminate possible culprit, I disabled DHCP and set IP adresses and
> the subnet mask manually.
>
> I also added another w2kPro and set to to Workgroup just to see if the
> problem is caused by the laptop which is on Domain. The problem persisted.
>
> 3. "To fix the problem, try using wins"
>
> I understand to use WINS I need to upgrade to w2k Server - is this
correct?
> If it is, then it seems to be an overkill, and the result is still not
> certain. If it is not, how do I use WINS on w2kPro - router - w2kPro
>
> 4. create entries in the lmhost files for computers offering shares
>
> I have been having these files from the very beginning.
>
> 5. What might happen to a network name? Obviously I have it and then it
just
> becomes unavailable. I understand, that whatever method is used for name
> resolution, the result is cached. And then this cache seems to get
> corrupted?
>
>
>
> "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
> news:G9P0c.96765$4o.118189@attbi_s52...
> > My guess [not knowing much about your setup] is that you have a netbios
> name
> > resolution problem. When you click shares in My Network Places, you are
> using netbios
> > name resolution and if you are not using wins on your network then you
are
> using
> > broadcasts to find computers. Broadcasting can be unreliable and should
be
> used only
> > in the smallest networks. When you enter \\computername\sharename ,
your
> computers
> > are probably using dns/host name resolution to find the other computers
> and seems to
> > work reliably. To fix the problem, try using wins on your network with
one
> wins
> > server on each subnet that are replication partners and also wins
clients
> to just
> > themselves. You also could have a problem with your master browser
> changing
> > frequently, which can cause network browsing problems. In a domain the
pdc
> fsmo
> > domain controller is the domain master browser and must not also be a
ras
> server or
> > be multihomed or browsing can fail. It would also need to be a wins
> client. Another
> > solution, depending on the size of your network would be to create
entries
> in the
> > lmhost files for computers offering shares. I would test that on one
> machine to see
> > if it helps as described in the last link See the links below on
> troubleshooting
> > browse problems and using lmhosts. -- Steve
> >
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;188305
> >
>
http://www.microsoft.com/resources/documentation/windows/2000/server/reskit/en-us/tcpip/part4/tcpappi.mspx
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;150800
> >
> > "aa" <aa@virgin.net> wrote in message
> news:%23oVIuW5$DHA.3400@tk2msftngp13.phx.gbl...
> > > Thanks, Steven,
> > > I think we are onti something.
> > > 1. Indeed when I use \\IPaddress\sharename in the Start-Run, I am
> getting
> > > Internet Explorer which shown the contents of the sharename folder and
I
> can
> > > browse and open files in it.
> > >
> > > If I click on the same folder in My network
> > > Places -->...ComputerName -->sharename I am getting
> > > "The specifed network name no longer available"
> > >
> > >
> > > 2 However if I run in the run box \\ComputerName\sharename it still
> works -
> > > does that mean the the ptoblem is still with the name resolution?
> > >
> > > 3. I would like to stress NO LONGER in the error message.
> > > Ideed, I often have it working, i.e. the name IS available. And
suddenly
> it
> > > becomes no longer available.
> > >
> > > 4. I ping ComputerName on which that \\ComputerName\sharename becomes
> > > unavailable, and it pings OK.
> > >
> > > What would be your comments?
> > >
> > > "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
> > > news:y%p0c.441224$na.1053698@attbi_s04...
> > > > You would have to find the IP address of the server offering the
share
> by
> > > either
> > > > running ipconfig /all on it or trying to ping it by name which if
> > > successful will
> > > > show the ip address. Them enter the unc address in the run box to
see
> if
> > > it brings up
> > > > the share. If the IP address is 192.168.1.55 enter
> > > \\192.168.1.55\sharename [using
> > > > actual sharename you are trying to access] in the run box.
> > > >
> > > > Netstat -s output looks OK in not indicating a lot of errors or
> > > retransmits, but it
> > > > does show 8 failed connection attempts which may indicate a network
> > > connectivity
> > > > problem to the server offering the share. Pinging the server by IP
> address
> > > will rule
> > > > that out a "basic" network connectivity problem. --- Steve
> > > >
> > > >
> > > > <aa> wrote in message
news:egUOns4%23DHA.1956@TK2MSFTNGP10.phx.gbl...
> > > > > Thanks.
> > > > >
> > > > > 1. Try using ip address instead of name such as
> > > \\xxx.xxx.xxx.xxx\share.
> > > > >
> > > > > Where and how do I do it? it is not me who uses the above name. It
> is
> > > used
> > > > > automatically.
> > > > > All I do is expand MyNetwork Plases, then expand the computrer
name
> > > which
> > > > > shows me the list of folders shares. When I click on a folder, I
get
> > > this
> > > > > error.
> > > > >
> > > > > 2. I run netstat -s and it retured the following (I ommit all
lines
> > > which
> > > > > =0) - What conclusions can you draw from it?
> > > > >
> > > > > IP Statistics
> > > > > Packets Received = 14581
> > > > > Received Packets Delivered = 14581
> > > > > Output Requests = 12716
> > > > >
> > > > > ICMP Statistics
> > > > > Received Sent
> > > > > Messages 0 2
> > > > > Echos 0 2
> > > > >
> > > > >
> > > > > TCP Statistics
> > > > > Active Opens = 21
> > > > > Passive Opens = 2
> > > > > Failed Connection Attempts = 8
> > > > > Reset Connections = 5
> > > > > Current Connections = 4
> > > > > Segments Received = 14070
> > > > > Segments Sent = 12409
> > > > > Segments Retransmitted = 19
> > > > >
> > > > > UDP Statistics
> > > > > Datagrams Received = 506
> > > > > No Ports = 5
> > > > > Receive Errors = 0
> > > > > Datagrams Sent = 276
> > > > >
> > > > >
> > > > > "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
> > > > > news:JWw_b.375753$I06.4013204@attbi_s01...
> > > > > > It could be a name resolution problem across the router. Try
using
> ip
> > > > > address instead
> > > > > > of name such as \\xxx.xxx.xxx.xxx\share. If that helps you may
> want to
> > > add
> > > > > an entry
> > > > > > to the hosts file on each computer for the other computer. If
that
> > > does
> > > > > not help you
> > > > > > may be having network connectivity problems of some sort.
> Netstat -s
> > > may
> > > > > help by
> > > > > > showing if there are excessive errors or retransmissions. ---
> Steve
> > > > > >
> > > > > >
> > > > > > "aa" <aa@virgin.net> wrote in message
> > > > > > news:O%23cq9pl%23DHA.3828@TK2MSFTNGP10.phx.gbl...
> > > > > > > In my w2k1-router-w2k2 network I can access files from one w2k
> on
> > > > > another
> > > > > > > for some time and then suddenly next attempts result into an
> error:
> > > > > > >
> > > > > > > \\ComputerName\folderName
> > > > > > > The specified network name is nolonger available
> > > > > > >
> > > > > > > I have to reboot both computers and then same situation
repeats.
> > > > > > >
> > > > > > > What do I do about it?
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Home Net Probs - AGAIN!!
    ... > the subnet mask was 255.0.0.0 as per the previous problem, ... > standard reboot and default back to factory settings - no change. ... rebooted the first two computers, and the network came back to normal. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Home Net Probs - AGAIN!!
    ... >> HELP CAREY!!! ... >> the subnet mask was 255.0.0.0 as per the previous problem, ... > rebooted the first two computers, and the network came back to normal. ...
    (microsoft.public.windowsxp.network_web)
  • Re: The Hard Problem for Behaviorists
    ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
    (sci.cognitive)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: {workgroup}"...is not accessible" after removing NWLINK
    ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
    (microsoft.public.windowsxp.network_web)