[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 767
  • Last Modified:

OS/2 Warp 4 TCP/IP Problem

I have an OS/2 Warp 4 workstation from ActiveVoice running their Repartee voicemail system.

This box came prebuilt without TCP/IP installed.  I followed the instructions about running INSTALL.EXE from the OS/2 CD and successfully installed TCP/IP.

I was able to browse the Internet, ping local servers and be pinged.

When I attempt to back up the OS/2 box using ARCserve 7 for NetWare (the OS/2 box is running the ARCserve Universal Client Agent for OS/2) - I can use the ARCserve Manager to browse the file and directory structure on the OS/2 box perfectly (ARCserve Manager runs under Windows NT).

HOWEVER - when I actually run the backup job, ARCserve attempts to connect to the OS/2 box and then fails with an ARCserve error code - it also returns an OS/2 error code:  -123

Then the backup fails.

Funny thing is - when I took identical hardware and the OS/2 CD-ROM that shipped with the Repartee system and built up an OS/2 Warp 4 installation according to their instructions, I can get everything working perfectly - including a backup and file verify.

Obviously it's a configuration issue with OS/2 Warp 4 - however I am new to this OS so I have NO idea what to look for.  I did not see anything unusual in the CONFIG.SYS or the MPTCONFG.INI files between the two OS/2 boxes.

I'm stumped...

Points will be increased if necessary...
0
DSPoole
Asked:
DSPoole
  • 10
  • 4
  • 2
  • +3
1 Solution
 
magarityCommented:
I've seen networking not want to play nice when it's installed as an afterthought  instead of installed at the same time as the OS.

Hmm, I forget the fix, if I ever did figure it out.  Well, wait a few days and Otta will scan through this forum; maybe he'll know.  There isn't much traffic in ye olde 'OS2 General' anymore...  ah, for the good ol' days...
0
 
DSPooleAuthor Commented:
oh - it plays nice, just not with ARCserve.

btw:  here are a couple of lines from the ARCserve log file (debug mode):

Jun-20 13:53:09     80     Connect to server voicemail.sandiego.mycompany.com @
                           10.100.150.26 (TCP/IP)
Jun-20 13:53:09     80     [DEBUG] idx[0] - Send Access Request
Jun-20 13:53:09     80     [DEBUG] Idx[0] - To Receive ack
Jun-20 13:53:09     80     [DEBUG] idx[0] - Received ack -[123]
Jun-20 13:53:09     80     E15035 Request rejected by
                           voicemail.sandiego.mycompany.com, command: 123
Jun-20 13:53:09     80     [DEBUG] Terminate Connection


You can see where the connection begins and the connection ends.

It's not a DNS/HOSTS issue because the OS/2 box that I can back up has no entries anywhere.
0
 
magarityCommented:
Ah, that helps...  are you certain that the remote machine knows to accept requests from this OS/2 machine?  It looks more like a permissions problem than a networking problem.  Is there a firewall or proxy somewhere between the two that's killing this connection?  That's my strongest hunch at this point.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
DSPooleAuthor Commented:
Yeah, the remote does - at least it is accepting requests from the OS/2 box I built that I can back up.  Didn't do anything weird.

I am totally unfamiliar with OS/2 security and permissions - how do you look at them/set them/change them?

The OS/2 Warp 4 install is not the server version but the workstation version.  I am guessing that the default install allows full access to the system - but maybe the custom install that was done before I got here locked the file system down.

How do I open it up?

btw:  there is only a switch between the NetWare box and the OS/2 box.
0
 
OttaCommented:
> Request rejected by voicemail.sandiego.mycompany.com

Check the log-files on this server.
Maybe, it says more about "why" the OS/2 box
was not granted "permission" to talk to this server.

               
0
 
DSPooleAuthor Commented:
ARCserve log files from the NetWare server as to why it was not able to talk to the OS/2 box:

Jun-20 13:53:09     80     Connect to server voicemail.sandiego.mycompany.com @
                                            10.100.150.26 (TCP/IP)
                  Jun-20 13:53:09     80     [DEBUG] idx[0] - Send Access Request
                  Jun-20 13:53:09     80     [DEBUG] Idx[0] - To Receive ack
                  Jun-20 13:53:09     80     [DEBUG] idx[0] - Received ack -[123]
                  Jun-20 13:53:09     80     E15035 Request rejected by
                                            voicemail.sandiego.mycompany.com, command: 123
                  Jun-20 13:53:09     80     [DEBUG] Terminate Connection


Duplicate post from above.
0
 
OttaCommented:
> Duplicate post from above.

So I see.

Does the client on the OS/2 box write a log-file?
0
 
DSPooleAuthor Commented:
Good question - I'll have to see if it does.

Any idea what might be causing this?
0
 
DSPooleAuthor Commented:
Perhaps the moderator would be kind enough to answer my question then?
0
 
mikefromrichmondCommented:
If the -123 error is coming from OS/2, then here's what it means:

SYS0123: A file name or volume label contains an incorrect character.

EXPLANATION: The system does not accept characters displayed using
the keyboard combination ALT plus 0-32 or the following characters:

  \  /  [ ] : |  <  >  +  ; =  .  ?  *  "

ACTION: Correct the file name or volume label and retry the command.

Perhaps you have a file with a strange filename?
0
 
DSPooleAuthor Commented:
Finally - a post!

I'll check into it when I have a chance.

Thanks!!!
0
 
mikefromrichmondCommented:
I didn't notice until after I posted that the date was June 2001, not 2002 !!  Can't believe you're still interested in an answer.
0
 
clark5031Commented:
I was wondering if you had any problems installing the Arcserve OS/2 agent?  We are using Repartee as well, but when I attemp to install the agent from the Arcserve CD it prompts me for Acrserve Client OS/2 Agent disk half way through the install.  I did not receive any disks except for the CD from Arcserve.  Any help would be appreciated.

By the way, My name is Brian.

Thanks
0
 
DSPooleAuthor Commented:
yep, sure did have problems.

fortunately for you I figured out how to install it.

I wrote a doc on how to install the TCP/IP stack for OS/2 Warp, here is the excerpt on how to install the ARCserve OS/2 Agent:

The ARCserve Universal Client Agent for OS/2 cannot be installed from the ARCserve 7 CD.

Instead, obtain a 3½” 1.44MB floppy disk and perform a fresh format on it.  The disk must be labeled as INSTALL1.

From the ARCserve 7 CD, copy the contents of the \IntelOS2\OS2Agent directory to the floppy disk.

Shut down the ActiveVoice voicemail application.

Use the OS/2 Command Prompt and change over to the A: drive and use the SETUP command to start the Universal Client Agent installation:

     A:\>SETUP

The installation program will launch.

Press the Continue button to continue the client installation.

From the Install dialog box, select the ARCserve Client Agent for OS/2

Press the Install… button to begin the installation.

The setup program will copy the files as required.

When the file copy process is completed, the Install dialog box will prompt for the CONFIG.SYS to be updated.  The Update CONFIG.SYS box should be checked.

Press the OK button to complete the installation of the Universal Client Agent.

The Installation and Maintenance dialog will appear prompting a reboot of the OS/2 server.

Press the OK button to finish the installation.

Use the OS/2 Shutdown icon on the desktop to reboot the OS/2 server.

It may be necessary to minimize the ActiveVoice voicemail application and launch the ARCserve Client Agent manually.  When the client is active, maximize the ActiveVoice voicemail application.


Send your e-mail to novellrocks@yahoo.com and I'll send you the entire doc - complete with screen shots (from a digital camera no less).

I also found a solution to getting ARCserve to work on backing up an OS/2 box - install all the ARCserve server and Manager patches.  CA released a patch some point that actually got the feature to work.
0
 
clark5031Commented:
Did you ever get an answer to your post?  I am have the same problems with OS/2 allowing ArcServe access to the directory I would like to backup.  
0
 
DSPooleAuthor Commented:
Clark5031,

I have found out that during the course of events, Computer Associates created a patch at one point.

When I reinstalled my backup server (hardware crash) I downloaded and installed not only the server-based patches, but the patches for the ARCserve Manager.

At that point, not only was I able to see my OS/2 Warp server - but back it up without errors as well.

Thus, I recommend you install the ARCserve 7 patches.

0
 
clark5031Commented:
DSPoole,
Thanks for the prompt reply.  As for OS/2, is there a place to modify permissions?  

We are using ArcServe 2000 so I would assume that the patches for ver 7 came over to 2000?  

0
 
DSPooleAuthor Commented:
ARCserver 2000 is a Windows-based product.

there may be the possibility that they did patch ARCserve 2000 as well, but I cannot guarentee it.

I suggest you patch 2000 with the latest patches and try it.

As for OS/2 - not a clue...
0
 
clark5031Commented:
DSPoole,
Thanks for the prompt reply.  As for OS/2, is there a place to modify permissions?  

We are using ArcServe 2000 so I would assume that the patches for ver 7 came over to 2000?  

0
 
DSPooleAuthor Commented:
echo.... ;)
0
 
WesLennonCommented:
PAQed, with points refunded (100)

WesLennon
Director of Community Serrvices
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 10
  • 4
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now