| Thread | Last Post | Replies |
|
| HIS 2000 on Windows Server 2003 | 30 Jun 2004 17:48 GMT | 4 |
We are in the processing to upgrade our servers Windows 2000 to Windows Server 2003. Can I install HIS 2000 on Windows 2003 and is it supported ? Thanks Michel
|
| HIS without SNA server | 28 Jun 2004 21:50 GMT | 6 |
To MSFT experts, The site I am now working implements TCP/IP only. There is no SNA. Does it work for HIS 2004 with TCP/IP only??? thanks & regards,
|
| Wow... My questions must be too hard! | 24 Jun 2004 01:17 GMT | 1 |
Since my other questions have not received any answers, maybe a simplier one would suffice. Does anyone have or know of a quality white paper/setup guide in regards to setting up Password Synchronization between an AS400 (V5R2) and a Host Integration Server 2000 across a TCP/IP ...
|
| HIS2000 --> AS400 Single Signon | 23 Jun 2004 00:34 GMT | 2 |
Here is my environment= LAN: TCP/IP 10/100/1000 10BASE-T network Server1:
|
| Problem with password synchronization | 21 Jun 2004 20:19 GMT | 3 |
I've succesfully created a connection with our AS/400. Initially, passwrods are equal on both systems (Win2k and AS/400). I map an account using the provided tool, but when I
|
| Event 654 | 21 Jun 2004 16:48 GMT | 3 |
I've got SNA Server providing communication between a web server and a mainframe system through the LU6.2 protocol. Every five minutes or so, I get the following entry in the application log. Source: SNA Host Security Category: None Type: Warning
|
| HIS and XP Client for APPC connection | 21 Jun 2004 16:12 GMT | 3 |
1) Installed HIS on NT (Version 4.0) with connection to MF --> APPC connection --> Line is active HOST APPC and ASCH definitions ok 2) RUnning Program on HIS Server (APPC application) which manages through the CIPC definition to work with the host application (goes to DB/2 to
|
| HIS Failover White Papers | 18 Jun 2004 00:56 GMT | 2 |
Is there any documentation or white papers on HIS SNA server failover options or scenario's? I need to develop some failover options for several production environments. One uses TN3270 Only and the others standard SNA server client connectivity. Also can NLB be used between 2 ...
|
| SNA client Cmpatibility | 16 Jun 2004 20:22 GMT | 1 |
IS the Microsoft SNA client ver 3.0 (3.0.0.414) compatible with the HIS 2000 server. We are upgrading from SNA server 3.0 to HIS 2000, and i would be very happy, if I do not need to upgrade the client. Best regards Jørn Peder Jørgensen
|
| Release Date for HIS 2004? | 16 Jun 2004 20:20 GMT | 1 |
Is there any word as yet on when HIS 2004 will emerge from its beta cocoon and enter the world as a full-fledged and certified product?
|
| com.cfg looses information. | 15 Jun 2004 23:55 GMT | 3 |
Old Server - NT 4.0 SP6a / SNA 4.0 SP New Server - Windows 2003 Server / HIS Integration 2000 w/ SP Connection : DLS LU Type : TN3270 and SN
|
| HIS SP1 Installation | 14 Jun 2004 19:46 GMT | 4 |
When I try to install SP1 I get the following message: "The installation source for this product is not available. Verify that the service exists and that you access it". I've downloaded the service pack numerous times before and installed without a problem on other servers. ...
|
| HIS and APPC | 11 Jun 2004 15:16 GMT | 1 |
1) Have an APPC application which needs to work through a HIS connection to the mainframe (XP Client to the HIS Server to the Mainframe). 2) HIS server and Client installed ok 3) Have VTAM definitions (worked fine with SNA 3.0) - should work with HIS
|
| HIS Client Installation | 10 Jun 2004 16:46 GMT | 1 |
We had one W2K application server with HIS client installation for communicating to a SNA 3.0 server. After completed the HIS installation to the application server, a message displays to restart the Snabase, however, I can
|
| Changing domains with HIS 5.0 | 07 Jun 2004 23:40 GMT | 2 |
We have ran into a situation where we need to move our HIS server out of the domain it is currently in. Evidently there is some process that needs to be completed before this move. Unfortunately the original configuration was done by someone no longer with the company and this
|