CIFS mount is showing permission denied

[Team_of_5]

Hi,
we are trying to do the CIFS mount from windows machine to HPUX 11.23 server. Whenever we are putting the password of administrator of windows server its throwing the error below error.

# cifslogin batch administrator
Remote user administrator's password:
Logging in User: Server not connected!

# cifslogin 172.16.1.170 administrator
Remote user administrator's password:
Logging in User: UNIX: Connection timed out

[here batch is hostname of server IP 172.16.1.170]

while giving cifsmount command we are getting below error.
"Connecting Server: UNIX: No such device or address"

We are able to mount the same to differant HPUX servers without any issues.

windows server entry is presant on the /etc/hosts also. we have confirmed that the access has been provided full access from windows to everyone user.

[Shibin_2]

Have you joined this UNIX server to windows domain ?

[karthik87]

HI can anyoone give some hint on the issue. i am facing this issue in one of my server.this is bit urgent..any hint on this would be highly appreciated

[Team_of_5]

The windows system is in domain and we are getting the ping responce. After giving the password for the windows machine the above mentioned msg is showing...prior to that the windows system has been formatted and meanwhile we have changed the IP of the unix machine...

[Matti_Kurkela]

If you can ping the Windows server successfully, but any attempts to use its network services result in "connection timed out" and other errors, I would recommend checking the firewall settings first.

All modern Windows servers have Windows Firewall included in the operating system software. Any external firewalls in the network between the HP-UX server and the Windows server can likewise block the connections.

When you're trying to connect by name "batch", the cifslogin command must first try and find the IP address corresponding to that name. Depending on configuration, the cifslogin might use a Windows SMB/CIFS broadcast, a WINS request, a DNS lookup or a combination of them.

For example, if cifslogin uses the broadcast method and gets no answer at all (perhaps because of firewalls), then it must conclude the requested server is not available. In this case, the error message is directly generated by the cifslogin tool.

But when you're cnnecting by IP address, the name look-up step can be skipped and cifslogin can immediately attempt to connect to the Windows server. Because standard Unix TCP/IP networking functions are used for this, the timeout error response will also be one of the standard Unix error messages.

MK

[Team_of_5 · Accepted solution]

We are able to moun the CIFS after upgrading the cifsclient version to the latest now. Thanks to all for your guidance...