Windows shares on a multi-homed server

Hello, I'm having a problem connecting to my windows servers through
network shares. The server has two ethernet cards and is set up
properly in DNS/AD:

machine.company.local -> 192.168.1.100
machine.company.backend -> 192.168.100.100

I can connect to the machine's shares through "\\machine" or
"\\machine.company.local" but on "\\machine.company.backend" it fails
with

System error 1326 has occurred.
Logon failure: unknown user name or bad password

The user name/password is not a problem since it immediately works if I
connect across the first ethernet adapter.

Any suggestions? I'd like my daily backups copied across this backend
network.

-John Dailey

Multihomed servers have always been a problem for just that reason. You
have two IPs linked to one name. In NT you could fix it by disabling Netbios
over TCP/IP on one interface. With dynamic DNS you now also get the problem
with DNS names.

Your internal clients should only be using the local DNS and should only
see the server's local name. For backups you will need to do the same -
refer to the server by its internal name. File sharing should only be linked
to this internal IP (which appears to be the case if you can't see it using
the external name/IP).

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Hello, I'm having a problem connecting to my windows servers through
> network shares. The server has two ethernet cards and is set up
> properly in DNS/AD:
>
> machine.company.local -> 192.168.1.100
> machine.company.backend -> 192.168.100.100
>
> I can connect to the machine's shares through "\\machine" or
> "\\machine.company.local" but on "\\machine.company.backend" it fails
> with
>
> System error 1326 has occurred.
> Logon failure: unknown user name or bad password
>
> The user name/password is not a problem since it immediately works if I
> connect across the first ethernet adapter.
>
> Any suggestions? I'd like my daily backups copied across this backend
> network.
>
> -John Dailey
>