Internal Interface generating "Duplicate Name" error

[Jeff Cochran]

It appears when a caller connects to our RAS modem, a "Duplicate Name"
error is being generated. This kills all NetBIOS communication from
the LAN side to the server. Before I take the hike to the server's
location and check the server out, what specifically should I be
looking at that could cause this?

Thanks,

Jeff

 

[Marc Reynolds [MSFT]]

Hi,

Have your renamed the connection for your network from "Local Area Network"
to "Internal"? If so, you need to change the name to something other than
"Internal". RRAS uses the "Internal" name and this cannot be changed.

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Bill Grant]

When a remote user connects, the RAS "server" acquires an additional IP
for its internal interface (to act as the server end of the point-to-point
connection). By default, this connection will have Netbios over TCP/IP
enabled which effectively makes the machine multihomed. If it is a browse
master this causes the usual browsing problems of a multihomed browse
master.

If this machine must be a browse master, you can disable Netbios over
TCP/IP on the extra interface using a registry change.

To prevent Netbt on the RRAS interface.

Open Registry Editor.
Navigate to HKLM\System\CurrentControlSet\Services (continued next line)
\RemoteAccess\Parameters\Ip

Create a new REG_DWORD called DisableNetbiosOverTcpip
Set its value to 1

 

[Jeff Cochran]

It's not a master browser (or not supposed to be, it's a member server
in an NT domain...) but I'll check this, thanks.

Jeff

 

[Jeff Cochran]

Have your renamed the connection for your network from "Local Area Network"
to "Internal"? If so, you need to change the name to something other than
"Internal". RRAS uses the "Internal" name and this cannot be changed.

I don't think it's been changed, but I'll check into it. Thanks.

Jeff