SAMBA client errors after routing change on SAMBA server

[Arthur Luimes_2]

We have a HP 10.20 SAMBA server and a HP 11.00 SAMBA client. The server has two NIC's: one for production and one for the backup network. Since a change on the backup NIC's private address 192.168.0.1 (the network mask was changed from a C class domain to a B class domain), we are experiencing intermittent SAMBA errors from the client to the server. There is about one error every two days, which log in the clients system log as follows:
Mar 21 14:48:01 vmunix: NFS read failed for server : RPC: Timed out.
In addition, I have seen Oracle connections to the production NIC time out as well. A number of users have been plagued by these issues.

The SAMBA connections point to the server's production NIC, which was not changed, as far as I know. Is it possible that this change in IP network mask for the backup NIC is the cause of these problems?

Thanks,
Arthur Luimes

[harry d brown jr]

Did you change the netmask ?

can you provide a netstat -rnv from both HP systems?

Did you change /etc/hosts and/or DNS ??

Did you set up the gateway for 192.168 correctly on BOTH servers?

live free or die
harry d brown jr

[RAC_1]

From client which samba server ip you refer??
nslookup/ping samba server. Does it point to the ip addresses of the correct ip and not the one that changed??

Is there anything on server's syslog file??

Anil

[Arthur Luimes_2]

The syslog on the server shows no recent errors. The nslookup from the client to the server works fine. The nslookup from the server to the client does not work, but I believe this is not essential.
I have not done the change in netmask myself, but an external party doing HP-UX system management of the server did. They told me they used ifconfig to do it. They told me they have not changed DNS or gateway settings.

[Arthur Luimes_2]

This morning there was another error. This time the SAMBA error was accompanied with an Oracle performance problem (the server is also an Oracle server). It looks like this is not SAMBA related, but definitely is due to something in the network.
The intermediate firewall shows no errors. I'm starting to get very nerveous about this.

[harry d brown jr]

Again,

Did you change the netmask ?

can you provide a netstat -rnv from both HP systems?

Did you change /etc/hosts and/or DNS ??

Did you set up the gateway for 192.168 correctly on BOTH servers?


and YES, its VERY important that BOTH client and server can look each other up in DNS.

live free or die
harry d brown jr