Windows 2000 server unable to see its local or other network share

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a Windows 2000 Server, one of 3 with near identical configuration
(appart from the obvious IP structure). Two of the servers are able to share
folders and connect to shares on other machines. The Server in question has
got shares but cannot run to its own shares or the shares on other machines.
I can use NSLOOKUP to resolve hostnames for the other servers, I can resolve
and PING ip addresses from pinging host names. WINS is enabled. The problem
seems to be that the server in question cannot see other shares on the
network. I have an error in the system log that I have been unable to find
out specific info on:

The server could not bind to the transport
\Device\NetBT_Tcpip_{C397B079-ACF8-4E6F-92A6-1B167B07FF94} because another
computer on the network has the same name. The server could not start.

Can anyone help!?

Cheers
Martin.
 
You either have two machines with the same name or you have incorrect
entries in either the DNS Database of the WINS database.
 
No. Not as simple as that, unfortunately.

I have checked the WINS and DNS DB's there are no duplicate records.

As each server has 2 nics, one public and the other private, I have disabled
File and Print on the public facing adapters. This is what is causing the
error listed below. Another NetBT error is generated suggesting there is a
duplicate machine name on the network. This is caused by a master browser
election only seeing machines available on the first adapter it comes to.

The strange thing is, I can access all shares from one server without
problem. I cannot access the same shares from the other server.

I have no way of forcing election from one adapter. I have tried to use the
Browmon.exe tool from the 2k resource kit, but it is unable to generate
listings becuase of the multihomed server environment.

Any other suggestions?

Phillip Windell said:
You either have two machines with the same name or you have incorrect
entries in either the DNS Database of the WINS database.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Martin T Williams said:
I have a Windows 2000 Server, one of 3 with near identical configuration
(appart from the obvious IP structure). Two of the servers are able to share
folders and connect to shares on other machines. The Server in question has
got shares but cannot run to its own shares or the shares on other machines.
I can use NSLOOKUP to resolve hostnames for the other servers, I can resolve
and PING ip addresses from pinging host names. WINS is enabled. The problem
seems to be that the server in question cannot see other shares on the
network. I have an error in the system log that I have been unable to find
out specific info on:

The server could not bind to the transport
\Device\NetBT_Tcpip_{C397B079-ACF8-4E6F-92A6-1B167B07FF94} because another
computer on the network has the same name. The server could not start.

Can anyone help!?

Cheers
Martin.
Click to expand...
Click to expand...
 
Martin T Williams said:
No. Not as simple as that, unfortunately.

I have checked the WINS and DNS DB's there are no duplicate records.
Click to expand...

It wouldn't be a "duplicate" record. It would simply be a single record
with the wrong IP#. You machine boots up with a different IP# but sees its
own name associated with different IP# in either WINS of DNS and frieks out.
It is kind of like the Cat seeing itself in the mirror and thinking there is
another Cat.
As each server has 2 nics, one public and the other private, I have disabled
File and Print on the public facing adapters. This is what is causing the
error listed below.
Click to expand...

2 Nics? That is an extremely big red flag waving around there. Running two
Nic must be done exactly right. Do it wrong and you will have all kinds of
problems.

I'm sure that some of these things below you may have already done,..but
humor me for a bit...

The Internal Nic should be configured as:

1. The static IP#
2. The Default Gateway pointing to the ISP
3. *Unbind* Client For MS Networks and File and Print Sharing
4. No DNS or WINS settings. Leave them blank.

The External Nic should be configured as:

1. The Statically assigned internal IP#
2. The DNS and WINS settings pointing to the server(s) on the LAN
3. No Default Gateway
4. Must be set to be the top of the "priority list" in the Advanced
Properties
in the Networking Configuration. This is found at:

Network Places Properties --> Advanced from the top menu --> "Advanced
Settings..." from the dropdown menu ---In the upper window of the Adapters
and Bindings, use the side arrows to move the Internal Nic to the top of the
list.

Additional important things:
In the Configuration of you DNS Service you will find a Tab in the
Server's Properties called "Forwarders". Enter you ISP's DNS server
here,...this is the *only* place your ISP's DNS should appear in your
network.
 
Remove the ISP's DNS from the Nic. Use it in the "Forwarders List" in your
DNS Service Configuration as I described. It is important,..it isn't
"optional" ;-)
 
Back
Top