I have a Windows 2003 server that gives me a Server 2505 error on
startup, claiming a name conflict with a Canon iR6570 multifunction copy
machine. I looked over the TCP/IP settings on the copy machine and can't see
a problem. I am also unable to browse the network from the server. The
server has one NIC, does not have NetBEUI installed, and File and Print
Sharing is enabled. Another scanner on the network is unable to use SMB to
scan to the server. What could be causing this?

It's not the TCPIP settings that you want to look at, it's the computer name
itself. What's the name of the server? What's the name of the printer? Are
you using WINS? If so, is there an old or dupe entry in the WINS database?

The computer name is DELLSC1420; the printer name is quite different
(though I don't recall exactly what it is; probably the default name for
that model). That is why I am mystified; it's another of those errors that
seems to make no sense whatsoever. We are not using WINS on the server, and
the printer is not set to use it either. I have been tempted to install it,
as I have seen it make things run more smoothly even though logically it
should not be needed on an all-XP/2003 network.

Show quoteHide quote

Hi Andrew,

WINS actually does smoothen thinkgs out regarding eliminating NetBIOS
broadcasts because all WINS clients register their names to the WINS server
and first ask the WINS server when resolving a NetBIOS name.

Obviously there's a name conflict somewhere. Is the printer installed on the
server? Does the server have two NICs?

Ace

Hi, Ace--

        The printer is installed on the server, but I don't see anything odd
about it. The server has just one NIC. As far as I know, it never had more
than one. Really strange.

        -- Andrew

Show quoteHide quote

Was there or is RRAS installed?

Run and post the results of the following:
nbtstat -n

Ace

RRAS is installed but not configured. I could probably uninstall it;
we're using a Cisco PIX as our VPN endpoint. The result of nbtstat -n shows
this:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Solutions>netstat -n

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    10.0.61.2:135          10.0.61.2:3609         ESTABLISHED
  TCP    10.0.61.2:389          10.0.61.2:3176         ESTABLISHED
  TCP    10.0.61.2:389          10.0.61.2:3612         TIME_WAIT
  TCP    10.0.61.2:389          10.0.61.2:3613         TIME_WAIT
  TCP    10.0.61.2:445          10.0.61.21:1524        ESTABLISHED
  TCP    10.0.61.2:445          10.0.61.22:4952        ESTABLISHED
  TCP    10.0.61.2:445          10.0.61.23:3590        ESTABLISHED
  TCP    10.0.61.2:445          10.0.61.24:3532        ESTABLISHED
  TCP    10.0.61.2:445          10.0.61.25:1139        ESTABLISHED
  TCP    10.0.61.2:1025         10.0.61.2:1082         ESTABLISHED
  TCP    10.0.61.2:1025         10.0.61.2:1426         ESTABLISHED
  TCP    10.0.61.2:1025         10.0.61.2:3610         ESTABLISHED
  TCP    10.0.61.2:1082         10.0.61.2:1025         ESTABLISHED
  TCP    10.0.61.2:1426         10.0.61.2:1025         ESTABLISHED
  TCP    10.0.61.2:3176         10.0.61.2:389          ESTABLISHED
  TCP    10.0.61.2:3389         10.0.61.211:1857       ESTABLISHED
  TCP    10.0.61.2:3540         10.0.61.2:389          CLOSE_WAIT
  TCP    10.0.61.2:3605         10.0.61.2:80           TIME_WAIT
  TCP    10.0.61.2:3607         10.0.61.2:80           TIME_WAIT
  TCP    10.0.61.2:3608         10.0.61.2:445          TIME_WAIT
  TCP    10.0.61.2:3609         10.0.61.2:135          ESTABLISHED
  TCP    10.0.61.2:3610         10.0.61.2:1025         ESTABLISHED
  TCP    10.0.61.2:3612         10.0.61.2:389          TIME_WAIT
  TCP    127.0.0.1:389          127.0.0.1:1030         ESTABLISHED
  TCP    127.0.0.1:389          127.0.0.1:1031         ESTABLISHED
  TCP    127.0.0.1:389          127.0.0.1:1032         ESTABLISHED
  TCP    127.0.0.1:389          127.0.0.1:3175         ESTABLISHED
  TCP    127.0.0.1:1030         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1031         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1032         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1085         127.0.0.1:40000        ESTABLISHED
  TCP    127.0.0.1:3175         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:3604         127.0.0.1:6999         TIME_WAIT
  TCP    127.0.0.1:3606         127.0.0.1:6999         TIME_WAIT
  TCP    127.0.0.1:5152         127.0.0.1:3210         CLOSE_WAIT
  TCP    127.0.0.1:40000        127.0.0.1:1085         ESTABLISHED


Show quoteHide quote

I was actually looking for an nbtstat -n.

Yes, uninstall/disable RRAS.That could be creating a duplicate entry for the
printer, so it's probably broadcasting same name with different IPs on the
interface(s) that RRAS creates.

Ace

An nbtstat -n shows no names in the cache and no duplicates. I'll
see about uninstalling RRAS.

        -- Andrew

Show quoteHide quote

Just checked-- RRAS is disabled. Might still be worth uninstalling,
though.

Show quoteHide quote

No, disabling it is fine. Kind of out of suggestions. Dupe names are based
on broadcasts finding it. So I don;t know about the printer, but I thought
originally it was because of multiple interfaces due to RRAS where the
printer name came up with this server's IP address since it was installed
and shared out.

If you had shut off the printer for an hour, does it still show a dupe name
error? Maybe there's something else out there with a dupe name?

Ace

Tomorrow, I'm going to try shutting off the printer and then
restarting the server while it is shut down. I won't be able to wait fifteen
minutes, but maybe if the server goes up first it will at least make the
server work right. This is really a weird one; thanks for all your
suggestions.

        -- Andrew

Show quoteHide quote

Your're welcome. Keep us posted with your results.

Ace

I shut down both the Canon iR6570 and another Canon multifunction
unit, an iR1023 that would not scan via SMB to the file server (that was the
big problem, and I believe that it was somehow related to the conflict with
the 6570), and then I restarted the file server. Everything worked fine
after that. I can browse the network from the server, the conflict message
went away, and scanning works from the Canon iR1023. I guess the solution
for now is to shut down the 6570 and maybe the 1023 whenever the server is
restarted. Not elegant, but at least it worked.

        -- Andrew

Show quoteHide quote

Then it appears obvious that the problem lies with the 6570. What is it's
name? Is it shared out directly or through the server?

ace

Multiple NICs in same segment server 2008
Taking ownership of files on remote computer
Group Policy logon script not applied if connected by WiFi
Multi-WAN loadbalancing & RRAS.
Routing and Remote Access NAT - I need to modify TTL
Remote AD offline and lack of access to local file server
VPN/RRAS, Workgroup mode
Reseting LAN interface count Windows 2000 server
shared drive problem
Creating an account on new computer from old computer