Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SNA client continuing on/ off session

Status
Not open for further replies.

ryan77

IS-IT--Management
Mar 26, 2003
2
MY
Hi, I'm be working in a company that using SNA server 4.0 as a gateway in NT 4.0 environment for sometime and has been working fine. Recently, almost all the users from branches have complaint that their connection session to host continuing On and Off. In the worse case, it could be happen 20 times per day. It happens intermitently and randomly to all servers and client.

After I checked Event viewer in SNA server the following warnings has been captured:

1) 1133 Message Sequence Error, Event ID 4
The node received a request with an invalid sequence number

2) Event ID 1021, The Node received a duplicated RU message number 1 from DLC.

3) 1132 Message Sequence Error, The Node received an FMD or DFC request when the data traffic state was not active.

FYI, our users are using Eicon Aviva as emulation programme and SNA server client 4.0 to connect SNA server. Any Idea will be highly apprecaited.

THnaks
 
I will be very interested in finding out what you find. I have been getting similar "message routing" errors only not nearly so frequently. One guy at Microsoft said it was caused by a client application problem. Something to do with CPI-C programming. I will look for the responses that I have gotten from Microsoft on this and send response. Do they have users trying to do screen scraping applications with active-x or other means. It seems that the messages we get started after the departmental programmers started writing new apps.
 
Thanks for your sharing. Anyway the problem seems to be fixed after we found out that one of the SNA Server still running in SP2. After we patched the SP4 the problem has disappear. Meanwhile, our WAN team also replace some parts in the router, but honestly I quite not convince that this is the source problem.

Regarding the programming parts, I'm feel sorry that I can't help since I'm from the administrators side. Anyway, hopefuly you may found the real answer for this and share out with us. Thanks you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top