Can not connect on socket (25)

[jacksors]

All of my Windows Server 2003 32bit clients are getting a "can not connect on socket (25)" error when using NetBackup 6.5. All other clients are working as they should. Please advise on what I should do. I followed all the troubleshooter steps, nothing has helped.

[Omar_Villa]

check the following

ping <master and media> 

nslookup <master and media>

bpclntcmd -pn

bpclntcmd -self

bpclntcmd -hn <master and media>

bpclntcmd -ip <IP of master and media>

run this and paste it backup, normaly socket error 25 can be a DNS issue with your media server.

let us know.

regards.

[jacksors]

Results:

C:\Program Files\Veritas\NetBackup\bin>ping blfhpcv01

Pinging blfhpcv01.domain.com [172.24.2.37] with 32 bytes of data:

Reply from 172.24.2.37: bytes=32 time<1ms TTL=128
Reply from 172.24.2.37: bytes=32 time<1ms TTL=128

Ping statistics for 172.24.2.37:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Program Files\Veritas\NetBackup\bin>ping blfhpcv01.domain.com

Pinging blfhpcv01.domain.com [172.24.2.37] with 32 bytes of data:

Reply from 172.24.2.37: bytes=32 time<1ms TTL=128
Reply from 172.24.2.37: bytes=32 time<1ms TTL=128

Ping statistics for 172.24.2.37:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Program Files\Veritas\NetBackup\bin>nslookup blfhpcv01
Server:  domainad1.domain.com
Address:  172.24.1.165

Name:    blfhpcv01.domain.com
Address:  172.24.2.37

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn
expecting response from server blfhpcv01
blfhpicm01.domain.com blfhpicm01 172.24.2.38 4111

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -self
gethostname() returned: blfhpicm01
host blfhpicm01: blfhpicm01.domain.com at 172.24.2.38 (0x260218ac)
aliases:

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn blfhpcv01
host blfhpcv01: blfhpcv01.domain.com at 172.24.2.37 (0x250218ac)
aliases:

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 172.24.2.37
checkhaddr: host   : blfhpcv01: blfhpcv01.domain.com at 172.24.2.37 (0x250218
ac)
checkhaddr: aliases:

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

[Omar_Villa]

Is your master server the media server also? if not you need to check that media too 

from the master try:

telnet <client name> bpcd

and try the bpclntcmd's to the client from the master

[jacksors]

Master and media are the same server.

Results from master to client 

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn
expecting response from server blfhpcv01
BLFHPCV01.domain.com blfhpcv01 172.24.2.37 1776

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -self
gethostname() returned: blfhpcv01
host blfhpcv01: BLFHPCV01.domain.com at 172.24.2.37 (0x250218ac)
aliases:

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn blfhpicm01
host blfhpicm01: blfhpicm01.domain.com at 172.24.2.38 (0x260218ac)
aliases:

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 172.24.2.38
checkhaddr: host   : blfhpicm01: blfhpicm01.domain.com at 172.24.2.38 (0x2602
18ac)
checkhaddr: aliases:

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

when I type telnet blfhpicm01 bpcd from the master it goes to a blank screen. Any key stroke exits the session.

[Omar_Villa]

how are your services doing? can u paste bpps -x output so we can see if vmd is running, how many drives are available? paste vmoprcmd -devconfig -l and vmoprcmd -d

You can also check the timout that you have configured for windows, go to the end of this page

http://seer.entsupport.symantec.com/docs/264886.htm

let us know.

regards.

[jacksors]

C:\Program Files\Veritas\NetBackup\bin>bpps -l
Performance Data for BLFHPICM01
Tuesday, October 28, 2008 7:41:27 AM
bpinetd:
        Processor time: 0.000000%
        Total processor time: 0.093750 seconds
        User time: 0.000000%
        Total user time: 0.015625 seconds
        Privileged time: 0.000000%
        Total privileged time: 0.078125 seconds
        Peak virtual bytes: 41021440
        Virtual bytes: 38957056
        Page faults per second: 0.000000
        Peak working set: 5283840
        Working set: 5283840
        Peak page file: 2707456 bytes
        Page file: 2707456 bytes
        2707456 Private bytes
        15 threads
        Priority base: 8
        Elapsed Time:  291.049750 seconds
        Process ID: 1408
        Paged pool: 24980 bytes
        Non-paged pool: 98728 bytes
        159 open handles
bpjava-msvc:
        Processor time: 0.000000%
        Total processor time: 0.015625 seconds
        User time: 0.000000%
        Total user time: 0.000000 seconds
        Privileged time: 0.000000%
        Total privileged time: 0.015625 seconds
        Peak virtual bytes: 41705472
        Virtual bytes: 39608320
        Page faults per second: 0.000000
        Peak working set: 4640768
        Working set: 4608000
        Peak page file: 1974272 bytes
        Page file: 1957888 bytes
        1957888 Private bytes
        7 threads
        Priority base: 8
        Elapsed Time:  287.690375 seconds
        Process ID: 1712
        Paged pool: 31640 bytes
        Non-paged pool: 66096 bytes
        110 open handles
bpps:
        Processor time: 0.000000%
        Total processor time: 0.015625 seconds
        User time: 0.000000%
        Total user time: 0.015625 seconds
        Privileged time: 0.000000%
        Total privileged time: 0.000000 seconds
        Peak virtual bytes: 22917120
        Virtual bytes: 22917120
        Page faults per second: 11.911871
        Peak working set: 2957312
        Working set: 2940928
        Peak page file: 1150976 bytes
        Page file: 1150976 bytes
        1150976 Private bytes
        2 threads
        Priority base: 8
        Elapsed Time:  1.038503 seconds
        Process ID: 4140
        Paged pool: 19356 bytes
        Non-paged pool: 3176 bytes
        109 open handles

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

My time wait value is set to 30.

[jacksors]

Previous post was output from the client.

This is output from the master

C:\Program Files\Veritas\Volmgr\bin>vmoprcmd -devconfig -l
Device Robot Drive       Robot                    Drive                Device

Type     Num Index  Type DrNum Status  Comment    Name                 Path

robot      0    -    TLD    -       -  -          -                    {0,0,4,1}

  drive    -    0  hcart    1      UP  -          IBM.ULT3580-TD4.000  {0,0,4,0}

C:\Program Files\Veritas\Volmgr\bin>vmoprcmd -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart    TLD                -                     No       -         0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 IBM.ULT3580-TD4.000   No       -

C:\Program Files\Veritas\Volmgr\bin>

C:\Program Files\Veritas\NetBackup\bin>bpps
* BLFHPCV01                                             10/28/08 09:19:30.314
COMMAND           PID      LOAD             TIME   MEM                  START
dbsrv9           1404    0.000%            0.781   11M  10/28/08 07:59:49.250
bmrd             1432    0.000%            0.078   11M  10/28/08 07:59:49.500
bpcompatd        1824    0.000%            0.031  9.3M  10/28/08 07:59:53.484
bpinetd          1868    0.000%            0.031  4.4M  10/28/08 07:59:53.562
bpjava-msvc      1964    0.000%            0.031  3.5M  10/28/08 07:59:56.734
bprd             2012    0.000%            0.062   11M  10/28/08 07:59:58.171
vmd              2032    0.000%            0.031   10M  10/28/08 07:59:58.328
bpdbm            2844    0.000%            0.093   11M  10/28/08 08:00:01.765
ltid             3024    0.000%            0.062   13M  10/28/08 08:00:02.171
bpjobd           3044    0.000%            0.031   11M  10/28/08 08:00:02.281
nbemm            3096    0.000%            0.625   24M  10/28/08 08:00:02.375
nbevtmgr          900    0.000%            0.203   15M  10/28/08 08:00:03.187
nbjm             1096    0.000%            0.125   13M  10/28/08 08:00:03.437
nbpem            4164    0.000%            0.250   17M  10/28/08 08:00:03.765
nbrmms           4228    0.000%            0.187   19M  10/28/08 08:00:03.984
nbproxy          4280    0.000%            0.156   13M  10/28/08 08:00:04.031
nbrb             4344    0.000%            0.078   17M  10/28/08 08:00:04.468
nbsl             4512    0.000%            0.062   18M  10/28/08 08:00:04.953
nbsvcmon         4732    0.000%            0.125   10M  10/28/08 08:00:05.578
nbstserv         4756    0.000%            0.093   16M  10/28/08 08:00:05.750
nbproxy          4772    0.000%            0.031   11M  10/28/08 08:00:05.812
nbvault          4908    0.000%            0.015   13M  10/28/08 08:00:06.203
tldd             5628    0.000%            0.031   10M  10/28/08 08:00:09.750
avrd             5636    0.000%            0.046   10M  10/28/08 08:00:09.781
tldcd            5652    0.000%            0.062   11M  10/28/08 08:00:10.875
NBConsole        5240    0.000%            6.171   36M  10/28/08 08:05:33.531
bpps             5644    0.000%            0.015  2.2M  10/28/08 09:19:29.298

[Omar_Villa]

I dont see the PBX daemon running, confir you can see it with bpps -x  if is not up you can started with

To stop the pbx_exchange daemon:

# /opt/VRTSpbx/bin/vxpbx_exchanged stop

To start the pbx_exchange daemon:

# /opt/VRTSpbx/bin/vxpbx_exchanged start

[sdo]

Stop and restart PBX on Windows with "services.msc" or:

> net stop "Symantec Private Branch Exchange"

> net start

> REM to check that is has actually stopped/disappeared

> net start "Symantec Private Branch Exchange"

[sdo]

Do the Windows servers have reverse IP lookup registered in your DNS server(s)?

[jacksors]

Do this on the server or on the client?

when I ran the bpps -x command it just displayed the help command and did not generate any output.

[sdo]

Sometimes we get confused with commands and environments.

Omar's suggested restarting the PBX service, but he gave you a Unix command/switch combination.

In Unix, the command "bpps -x" will list all NetBackup daemons/processes and the PBX daemon.

Anyway, you are Windows, so use:

> net start

...to see if the PBX service is running.

...and see my earlier post on how to stop and restart the PBX service in Windows.

This might, or might not, solve your problem.  Omar suggested it because you've tried restarting the NetBackup services themselves with "bpup" and "bpdown", but these commands do not stop and/or start the PBX service - henmce the additional steps/command to accomplish this.

[jacksors]

Yes, all reverse DNS lookup zones are in DNS. Some of the clients that are failing are in the same subnet that working clients are. The only similarity I can see between clients is that they are runnin the 32bit version of Windows.

I restarted the PBX on both the server and the client. In Windows services console, the service was listed as started on both systems.

I am still receiving the same error.

[cannot_connect_]

hi,
This seems similar to my situation.

master : window 2003 server
media server : window 2003 server
NBU version : 6.5

SAN media server was not connected continually. And tape device was not active.
(admin console > host properties > media server double click)
I had to reboot the media server, and checked  pbx pkg, but no responses..
Therefore, installed NBU 6.5.2 patch on both master and media servers and it connected successfully.
Have you installed the maintanance patch 6.5.2 on master and media server??

[jacksors]

Yes the patch has been applied to the master/media server and the client. I'm fairly positive they were both rebooted afterwards, however I do not know. I know the services had all been restarted. I will restart the systems to verify. If no follow up post is added from me, it means it is still not working.

Thanks for everyone's input.