Networker fails to backup laptop with AT&T Communication Manager software.

You will need to do some tests and analysis to figure out where does it breaks... is it like portmapper issue or something like that. I do not use this software, but perhaps someone else who does can give us more information if they encountered this issue.

Scheduled backup (initiated from NW server) or manual backup (initiated from laptop) fails ? Or maybe both ?

The reason that the post is under Linda Collier name is that she has the only login account. I am setup under her as an alternate p.o.c.

We still have the same problem as stated.

I have a laptop with Windows XP running Networker 7.4. Networker was backing it up without any problems until the AT&T Comunication Manager software was installed on the laptop. Now it will no longer backup.

I removed the AT&T software and tried a backup and it backed up ok. I reinstalled the AT&T software and once again networker will not back it up.

I also tried unistalling and reinstaller networker with no luck.

We are also having the same problems with Verizon Communication software that is installed on some laptops.

Has anyone seen and know if a fix for this, other than unistalling the software.

thanks
Doug H.

The reason that the post is under Linda Collier name is that she has the only login account. I am setup under her as an alternate p.o.c.

We still have the same problem as stated.

I have a laptop with Windows XP running Networker 7.4. Networker was backing it up without any problems until the AT&T Comunication Manager software was installed on the laptop. Now it will no longer backup.

I removed the AT&T software and tried a backup and it backed up ok. I reinstalled the AT&T software and once again networker will not back it up.

I also tried unistalling and reinstaller networker with no luck.

We are also having the same problems with Verizon Communication software that is installed on some laptops.

Has anyone seen and know if a fix for this, other than unistalling the software.

thanks
Doug H.

It fails when you run it from networker....It works ok if you do a manual from the laptop.

What does the log ( Daemon.log) say.
Any error message?
What is the behaviour of the schedule backkup?
Does it start? Does it star then fails?
If so what error messages in the savegrp?
What port/s does AT&T uses?

Could you please paste output from following commands:
rpcinfo -p client_name (on NW server)
rpcinfo -p NW_Server (on NW client).

This is what I get when I run rpcinfo -p from the server.

rpcinfo -p rmlczd652120dh2
program vers proto port service
100000 2 tcp 7938 rpcbind
100000 2 udp 7938 rpcbind
390436 1 tcp 9335
390435 1 tcp 9818
390113 1 tcp 7937 nsrexec

and this is what I get when I run rpcinfo -p from the client.
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390436 1 tcp 9202
390435 1 tcp 8734
390113 1 tcp 7937
390115 1 tcp 9016
390103 2 tcp 9344
390109 2 tcp 9344
390110 1 tcp 9344
390120 1 tcp 9344
390109 2 udp 9168
390105 5 tcp 9696
390105 6 tcp 9696
390107 5 tcp 8991
390107 6 tcp 8991
390433 1 tcp 9301
390104 105 tcp 8049
390104 205 tcp 9398
390104 305 tcp 7979
390104 405 tcp 8083
390104 505 tcp 9128
390104 605 tcp 8174
390430 1 tcp 8842
390429 101 tcp 9449
390104 705 tcp 9686
390104 805 tcp 9418
390104 905 tcp 9743
390104 1005 tcp 8788
program vers proto port
100000 4 tcp 111
100000 3 tcp 111
100000 2 tcp 111
100000 4 udp 111
100000 3 udp 111
100000 2 udp 111
100024 1 udp 32772
100024 1 tcp 32771
100133 1 udp 32772
100133 1 tcp 32771
100021 1 udp 4045
100021 2 udp 4045
100021 3 udp 4045
100021 4 udp 4045
100021 1 tcp 4045
100021 2 tcp 4045
100021 3 tcp 4045
100021 4 tcp 4045
100011 1 udp 32781
100068 2 udp 32782
100068 3 udp 32782
100068 4 udp 32782
100068 5 udp 32782
100083 1 tcp 32772
390402 1 tcp 9001
390436 1 tcp 9202
390435 1 tcp 8734
390113 1 tcp 7937
390115 1 tcp 9016
390103 2 tcp 9344
390109 2 tcp 9344
390110 1 tcp 9344
390120 1 tcp 9344
390109 2 udp 9168
390105 5 tcp 9696
390105 6 tcp 9696
390107 5 tcp 8991
390107 6 tcp 8991
390433 1 tcp 9301
390104 105 tcp 8049
390104 305 tcp 7979
390104 205 tcp 9398
390104 405 tcp 8083
390104 505 tcp 9128
390104 605 tcp 8174
390430 1 tcp 8842
390429 101 tcp 9449
390104 705 tcp 9686
390104 805 tcp 9418
390104 905 tcp 9743
390104 1005 tcp 8788

Portmapper shows correct info. Do you have Windows XP firewall turned on (or maybe installation of AT&T software changes its settings) ? If so, try to turn it off (for a test) then try to start scheduled backup from server side. Another test you can perform is to telnet to ports 7937 and 7938 from server to client and check whether this connection is possible (check WinXP FW). You can also check if the name resolution after AT&T software installation works fine - especially from the client on which you had installed it.

I turned windows firewall off and retried still had the same problem.
I also was able to telnet to ports 7937 and 7938.
i also checked the name resolution after the ATT software was install and it was OK.
Anyone have any other suggestions?

I think you have to ask the support of AT&T software what it changes after installation. Especially what changes are made to network and security parameters. Does AT&T software has running services on WinXP? If there are such, try to stop them, then restart NW services and check if it will start working.