[williamc]

So far no one can figure this out, so maybe some of the guru's here can help.

I'm using a Canon IR5000 copy machine. It communicates with SMB to the windows network. Previously, with windows 2000 server, it could connect to and save documents to a share folder. Now with server 2003, it locks up when browsing to the server.

Microsoft and Canon both refered me to this knowledgebase article:
http://support.microsoft.com/?id=811497

I've performed these steps, but still no luck. The printer can browse all the other servers on my network, just not the 2003 PDC where all the edocuments are stored. Any and all suggestions are welcome!

William

[Seb7]

Might be a firewall issue.

[williamc]

no, these machines are on the same subnet.

[williamc]

This was tricky, but it got fixed. For those interested:

The SMB request was sent to the PDC, which caused the copy machine to lock up. I ran ethereal to watch the transaction and found that the request was fine, but the response was to a 169.x.x.x address. Running an SMB request on another server would respond with the correct address 192.x.x.x.

Turns out, that the secondary nic on the server was used during initial install, and was then unplugged. It assigned itself the exact same 169.x.x.x address that was being sent to the copy machine. How could an unused NIC send a response via the used and functional NIC? Well, the WINS cache had somehow grabbed the 169.x.x.x address and was using it to respond to the browse request. By utilizing the secondary WINS server, the problem went away.

Oh what fun this was to diagnose! Hope this helps someone that may experience the same problem.

William

[markjcb]

I had a similar problem and found out that the problem was due to the wins config on the server.

Browsing via workstations to the server only tests DNS and the copier uses Wins (Netbios) names to communicate.

To test that wins is configured correctly on the server download the nblookup tool from MS and run it on on any PC on your network.

http://support.microsoft.com/kb/830578

If you can not communicate with the server via wins then SMB will not work...