Mounting CIFS shares with IP address

[Bryan Strait]

Hi,

I'm not a guru by any means when it comes to windows networking. I've searched the forums and seen similar issues; each with the conclusion that CIFS shares cannot be mounted using only the IP address.

For example, the following works where server is resolved to 192.168.10.50 in the /etc/hosts file...

mount -F cifs server:/share /mnt/share

But the following produces a "connection refused" error...

mount -F cifs 192.168.10.50:/share /mnt/share

We're running version A.01.09 client running on HPUX 11i v2, connecting to shares on a Win2003 server. I can successfully mount the shares by hostname but not by IP. We're not using DNS, so the host name resolution is limited to /etc/hosts. The reason we need to mount by IP address instead of hostname is that I need shares to be mounted on specific IP addresses. When mounting by IP I get "connection refused."

Is there any way the CIFS client can be told which IP address to use? I've tried the ipaddr option with mount, but this only works as a netbios IP address. I've also tried using the cifsmount using the -I option and it also produces undesireable results. Furthermore, I've tried creating host entries in the /etc/hosts specific to the IP addresses we wish to mount - this still produces a connection refused.

Thanks so much!

Bryan

[Muthukumar_5]

Can you say for,

# rpcinfo -s
# rpcinfo -s

/etc/nsswitch.conf hosts: entry?

hth.

[Steven E. Protter]

Shalom Brian,

The windows box may have more than one IP address configured and be blocking via what Microsoft claims is a firewall on one of the IP addresses.

ipconfig /all

On the win box and see if this is the cae.

SEP

[Bryan Strait]

Steven,

The windows machine does have more than one IP address. I have what I believe it the entire Windows firewall disabled. Is it a Windows protection feature to only allow a user to connect on one interface at a time?

The HPUX machine running the CIFS client also has two interfaces, both of which can ping the Windows machine on both of it's interfaces. I noticed that which interface the CIFS client uses is dependent on the order of the /etc/hosts file.

Thanks again for the help.

Bryan

[Bryan Strait]

Muthukumar,

rpcinfo returns the same for the hostname and IP address of both subnet connections:

"rpcinfo -s host", "rpcinfo -s 192.168.13.50", and "rpcinfo -s 192.168.14.50" all return the same report:

program versions netids service owner
100000 2 tcp,udp rpcbind unknown
351455 2,1 udp,tcp - unknown
100005 3,2,1 tcp,udp mountd unknown
100021 4,3,2,1 tcp,udp nlockmgr unknown
100024 1 tcp,udp status unknown
100003 3,2,1 tcp,udp nfs unknown


The nsswitch file specifies to use local first, then DNS for hostname resolution.

Bryan