Re: The specified network name is nolonger available

aa
Date: 03/04/04 

Date: Thu, 4 Mar 2004 19:44:38 -0000

Roland,
1. I have no problems with pinging both using names or IP addresses
Problem arise when I am trying to acces files via Windows Explorer
Moreover after I, as Stiven suggested mapped drives using IP addresses
instead of computerNames, the "The specified network name is nolonger
available" does not occur any longer when I acces a network drive in
WindowsExplorer-->My Computer.

The problem still persists when I attempt to acccess these drives via My
Network Places or Computers near me. This does not bother me as I fail to
understand what these features are for as accessing drives is much easier
via My computer.

But mapping drives with IP address means that I cannot use DHCP. For the
moment this is not a problem too, but I am interested to understand why DHCP
is not working on my setup.
It looks like people covered every possibilities except the router - perhaps
its DHCP is corrupted?

2/ Try to ping by FQDN. This requires a domain. ping computer2.domain.com
> (domain.com is a variable, not a literal)

I do not have a domain. How do I set up one? Please mind that we are talking
abour w2kPro, not Server

3. \\server\share.
> Note: Server means server service. If a computer is running F&P Sharing,
> then it is running a F&P Sharing Service

You have confused me very thoroughly -please do not forget I am a layman.

Without going into too much details here, do you mean me trying
\\computerName\shared_folder_name in the command prompt, then this works
fine.

4. I am very much confused about sharing permissions. I started a separate
thead on this subject and people there assured me that EVERYONE should
suffice for my purpose. Are they wrong? So everyone does not actualy mean
everyone and I indeed need to set permissions on my peer-to-peer network?

"Roland Hall" <nobody@nowhere> wrote in message
news:eQtDsmeAEHA.640@TK2MSFTNGP09.phx.gbl...

> "aa" wrote in message news:%23DrnpWUAEHA.3712@tk2msftngp13.phx.gbl...
> : Matt, I was asking WHERE I should use IP adress instead of a name. Now I
> : guess you mean either in the run box or in the IE address field.
> : Yes, I can get it both ways, which according to your mesage means
> corrupted
> : netbios name cache
> :
> : How do I fix a corrupted netbios name cache ?
>
> You need to regroup.
>
> 1. If you cannot reach a computer on the LAN by name on another computer
and
> you're running TCP/IP, you try to get there by IP address. At a command
> prompt:
>
> Assuming computers are named computer1, computer2:
>
> a. First you try to ping the computer by name: ping computer2 - If that
> works, NetBIOS is working.
> b. If that fails, ping by IP address. ping 192.168.0.12 - If that works,
you
> have a NetBIOS naming issue.
> c. Try to ping by FQDN. This requires a domain. ping
computer2.domain.com
> (domain.com is a variable, not a literal)
>
> 2. If you can reach a computer on the LAN by name with UNC, then you are
> trying \\server\share.
> Note: Server means server service. If a computer is running F&P Sharing,
> then it is running a F&P Sharing Service. For the purpose of discussion,
> you can substitute server with computer if that helps your understanding.
>
> \\computer\share
>
> From a command prompt, you can try: dir \\computer\share
> If it fails, the SPECIFIC error helps you resolve the issue. Saying it
> doens't work, is not enough. It could require authentication, which
> requires that you have:
> Client for Microsoft Networks
> File and Printer Sharing...with a share that allows access to a specified
> user, (default everyone).
> You must either pass credentials when trying to connect or have the same
> credentials on both computers. (credentials = username, password). This
> user MUST have rights to access the share. It must also have NTFS rights.
> (File System Rights) to the path where the share is configured.
>
> You access file system rights by right-clicking, in Windows Explorer, on
the
> path where the share exists and select properties, then the security tab.
> The easy test is to try connecting with an account on the OTHER system to
> test your share configuration before you try to modify permissions for
> non-Admin users.
>
> Easy test: From a command prompt:
>
> net use * \\server\share password /u:domain\username /persistent:yes
>
> This will map the next available drive [computer1] to a share [computer2]
> using credentials configured on computer2 and make the mapping static
across
> reboots.
>
> So, if mapping from computer1 to computer2 using LOCAL domain [computer
> name] and administrator account, you can try a default administrative
share:
>
> net use * \\computer2\c$ password /u:computer2\administrator
/persistent:yes
>
> Note: password is a variable and should not be a literal unless your admin
> password is the word password. And, if so, chnage it. It's not a good
> idea.
> Note: c$ is a built-in administrative share located at the root of the C:
> logical drive.
>
> I wouldn't worry about master browser election candidacy in a workgroup.
> You want this to happen so it doesn't matter which computer is on or
first.
> In a domain, with a server, the DC should be the master and all
workstations
> should have this disabled. In fact, all servers that you do not want to
> participate should have this disabled also. It's not an issue with what
> you're doing now so don't worry about it.
>
> In a peer-peer network, you work exponentially harder as you add more
> workstations. If all users need to access all user's workstations, then
you
> have to create all user accounts on all workstations or use the same
account
> on all of them. NO, it's not recommended but it is possible and if you're
> the only one using the workstations, it's still not recommended but it is
> easier to work with.
>
> Computer1 can access computer2 if computer2 has an active share and user
on
> computer1 has an account on computer2. This does NOT imply that computer2
> has the same rights to computer1. You will have to duplicate your efforts
> on computer1, as you did on computer2 for the computer2 user. Having fun
> yet? (O:=
>
> That's all there is to it. You don't need WINS unless you want to browse
> across a subnet and unless you have a server, you don't have it. If you
> have a NAT/firewall router, you set it to provide IP addressing via DHCP,
> plug in your ISPs DNS server addresses and have it pass those with the
DHCP
> setup so you can access computers on the Internet by name. If you have
> NetBIOS over TCP/IP enabled on your clients, then you can access the
> computers by name, otherwise you must use an IP address.
>
> HOSTS = TCP/IP
> LMHOSTS = NetBIOS
>
> You will not need to use your HOSTS file, to connect to your other system.
> You can however use an LMHOSTS file, but it is not required since you're
in
> the same subnet.
>
> This is FYI per your last request re: NetBIOS cache.
>
> NetBIOS cache: (From a command prompt)
> nbtstat -c
> This will show you what is in cache.
>
> How do you modify it? Edit your LMHOSTS file. You must also have your
> TCP/IP settings set to use the LMHOSTS file. It is located on the WINS
tab
> of the Advanced TCP/IP settings.
> Your LMHOSTS file is located at: %systemroot%\system32\drivers\etc\lmhosts
> It does not exist by default. There is a sample, lmhosts.sam. It
provides
> some examples.
> LMHOSTS must not have an extension or it will not work.
>
> After you make an edit, using Notepad. Save your changes and at a command
> prompt type in:
> nbtstat -R
> Note: R must be uppercase.
>
> You can then check to see if your changes were added as you expected with:
> nbtstat -c
>
> If you cannot get it from here, then show EXACTLY what you tried and
EXACTLY
> what happend including any/all EXACT error messages. Do not interpret or
> generalize.
>
> You still have not shown your ipconfig /all settings for your computers.
> Telling us it is the same eliminates anyone else being able to catch an
> error you might have overlooked.
>
> Good luck...HTH...
>
> --
> Roland Hall
> /* This information is distributed in the hope that it will be useful, but
> without any warranty; without even the implied warranty of merchantability
> or fitness for a particular purpose. */
> Online Support for IT Professionals -
> http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
> How-to: Windows 2000 DNS:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
>
>
>

Relevant Pages

  • Re: Computer \computername cannot be managed because it is not running Windows NT
    ... the other computer/client which 'wants' to manage it via Server ... 'NetBIOS over TCP/IP' is disabled. ... little to nothing to improve network security. ... disabling 'NetBIOS over TCP/IP' and therefore loosing 'My Network ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Cannot browse the network after migration
    ... the cause is the multiply NICs are all enable NetBT. ... >>> browse the network. ... >>> 189101 Understanding NetBIOS Resource Record Flags ... >>> NetBIOS setting from the DHCP server. ...
    (microsoft.public.windows.server.migration)
  • FIXED: Not all computers see server...
    ... The NETBIOS over TCP/IP cured the problem and retained my firewall ... > domain mixed-mode network with DHCP and DNS, ... This was due to needed to connect with older machines ... After installing the server software and making the new server ...
    (microsoft.public.windows.server.networking)
  • RE: WINS 4204 Every 40 Minutes
    ... Windows NT Technology based server, it automatically sends IGMP packets to ... I think it's unnecessary to run WINS server in the network. ... NetBIOS name resolution service that allows client computers to register ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: name resolution order
    ... WINS server ... A Windows computer assumes you are seeking to resolve a NetBIOS name unless ... search order becomes, cache, hosts file, DNS server, and yup - lmhosts file. ...
    (microsoft.public.win2000.networking)