Getting error “FILE WRITE READ” CODE 59

[nbustarter380]

 Hello,

 I am trying to get a Windows 2008 server to connect to our NBU server.

  I can ping the Windows 2008 server from our NBU master server however I can’t ping or NBU server from the wndows client.

 Here is some information from the Windows 2008 client server

 C:\>ping nbupower2.oit.state.nj.us

Pinging nbupower2.oit.state.nj.us [127.x.x.xxx] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 127.x.x.xxx:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn nbupower2.oit.state.nj.us

host nbupower2.oit.state.nj.us: nbupower2.oit.state.nj.us at 127.x.x.xxx

aliases:     nbupower2.oit.state.nj.us     127.x.x.xxx

D:\Program Files\Veritas\NetBackup\bin>bpclntcmd   -self

gethostname() returned: s00asr07.xxx.xx.xxx

host s00asr07.xxx.xx.xxx: s00asr07.xxx.xx.xxx at 2002:7e06:664::7e06:664

host s00asr07.xxx.xx.xxx: s00asr07.xxx.xx.xxx at 127.x.x.xxx

host s00asr07.xxx.xx.xxx: s00asr07.xxx.xx.xxx at 11.45.183.176

aliases:     s00asr07.xxx.xx.xxx     2002:7e06:664::7e06:664     127.x.x.xxx

   11.45.183.176

getfqdn(s00asr07.xxx.xx.xxx) returned: s00asr07.xxx.xx.xxx

D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn

D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip nbupower2.oit.state.nj.us

host nbupower2.oit.state.nj.us: nbupower2.oit.state.nj.us at 127.x.x.xxx

aliases:     nbupower2.oit.state.nj.us     127.x.x.xxx

From our NBU (Linux) core server

 [otvnewman@nbupower2 ~]$ sudo su -

[root@nbupower2 ~]# ping s00asr07.xxx.xx.xxx

PING s00asr07.xxx.xx.xxx (127.x.x.xxx) 56(84) bytes of data.

64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=1 ttl=128 time=0.494 ms

64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=2 ttl=128 time=0.300 ms

64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=3 ttl=128 time=0.297 ms

64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=4 ttl=128 time=0.298 ms

64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=5 ttl=128 time=0.272 ms

64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=6 ttl=128 time=0.288 ms

64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=7 ttl=128 time=0.258 ms

^C

--- s00asr07.xxx.xx.xxx ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 6485ms

rtt min/avg/max/mdev = 0.258/0.315/0.494/0.075 ms

[root@nbupower2 ~]# nslookup

[root@nbupower2 ~]# nslookup s00asr07.xxx.xx.xxx

Server:         11.25.15.23

Address:        11.25.15.23#53

Name:   s00asr07.xxx.xx.xxx

Address: 11.45.183.176

[root@nbupower2 ~]# bptestbpcd -client s00asr07.xxx.xx.xxx

<16>bptestbpcd main: Function ConnectToBPCD(s00asr07.xxx.xx.xxx) failed: 46

server not allowed access

[root@nbupower2 ~]#

Fyi – Netbackup version is 7.5 for both the client and the master server

nbupower2= our Linux master server

s00asr07 = the windows 2008 server

Thanks for any help!

[revarooo]

[root@nbupower2 ~]# bptestbpcd -client s00asr07.xxx.xx.xxx

<16>bptestbpcd main: Function ConnectToBPCD(s00asr07.xxx.xx.xxx) failed: 46

server not allowed access

This means the connection is getting to the client 's00asr07.xxx.xx.xxx' but it is being rejected because that client does not have a SERVER entry for the server 'nbupower2'

Have you added this? Check the incoming connection in the netbackup\logs\bpcd\ log file. Does the client resolve that IP to the hostname in the SERVER list?

[Marianne]

I can’t ping or NBU server from the wndows client.

Speak to your server and network admins... 

Nothing is going to work until such time as network connectivity works both ways.

If you have separate media server, check connectivity in all directions.

bpcd log on the client will help to see reverse lookup on Client and SERVER lookup.

[nbustarter380]

Thanks,

revaroo, marianne

For some reason I can seem to create the bpcd log file on the client this is the command right >>:bpcd? 

when I enter the command

D:\Program Files\Veritas\NetBackup\bin>:bpcd

I just get the following

D:\Program Files\Veritas\NetBackup\bin>

Thanks

[Marianne]

Small correction:

bpcd log folder needs to be created in D:\Program Files\Veritas\NetBackup\logs. 

Next time a connection request is received, a new log file will be created in this folder:
<date>.log

Please copy this log file to bpcd.txt and post as File attachment.

[revarooo · Accepted solution]

nbustarter, you need to create a folder in the D:\program files\veritas\netbackup\logs\ directory called bpcd.

Once that is created, rerun the bptestbpcd -client s00asr07.xxx.xx.xxx

If it fails with "Server not allowed access", check the bpcd log file in the bpcd directory. You should see the incoming IP address. Check on the client what hostname this IP address resolves to.

You can use netbackup\bin\bpclntcmd -ip <ip_address>   that will tell you.

the hostname should be in the SERVER list on the client.

[revarooo]

Whoops, corrected. Typing to quickly and brain not engaged :)

[Karthikeyan_Sun]

Also there is a IP mismatch on this !! is this lookup getting it from local host file or from DNS? is there any host entry made on the client server?

[root@nbupower2 ~]# ping s00asr07.xxx.xx.xxx

PING s00asr07.xxx.xx.xxx (127.x.x.xxx) 56(84) bytes of data.

64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=1 ttl=128 time=0.494 ms

[root@nbupower2 ~]# nslookup s00asr07.xxx.xx.xxx

Server:         11.25.15.23

Address:        11.25.15.23#53

Name:   s00asr07.xxx.xx.xxx

Address: 11.45.183.176

On there hand, there can be an infra who restricts ICMP Ping access and give access only to the netbackup ports; might be yours is one among that. Did you make sure to add up the correct media/master server name

http://www.symantec.com/business/support/index?page=content&id=TECH39392

[nbustarter380]

Thanks revaroo, marianne and Karthikeyan for your responses I appreciate it!

Karthikeyan, There was a typing error on my part  with the IP mismatch  (sorry) there is a host entry made on  the client server.

The issue has been resolved we changed the client server IP and put it on a new VLAN tier and I contacted the Network Admin (as suggested by Marianne) and they made the appropriate changes.

Thanks again for your assistance