General discussion

Locked

PCANYWHERE TCP/IP SERVER UTILIZATION

By EPAIT ·
I am trying to give remote access to desktops using a TCP/IP connection with either PCANYWHERE or VNC. Each of the workstations on my lan have a static IP address which I configured the remote software to search for.

The problem I have is serverutilization on my Netware 5 LAN. I am running IP/IPX on my lan and when I set a windows 9x client up with PCANYWHERE to open when windows is started, using a waiting for a TCP/IP connection, my server shows high utilization when my log in screen comes up prior to logging into the network. 35% to 40% utilization. As soon as you log in the utilization goes back to normal. I have tried configuring a dial up client on my network to access my PC via the Internet using TCP/IP. If the host is logged into the network PCANYWHERE can access the desktop. If the host is not logged in, PCANYWHERE times out trying to locate my desktop. I want to be able to have users reboot their station and have the logon screen up but not be logged in with PCANYWHERE running in the background waiting for a TCP/IP connection. This will allow users to access their desktops after hours with no security risk of leaving people logged into the network. Besides I run a backup tape everynight and the Watchdog program logs any users off prior to running.


thanks,
Rob CNE3

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

PCANYWHERE TCP/IP SERVER UTILIZATION

by erikdr In reply to PCANYWHERE TCP/IP SERVER ...

The behaviour of the NetWare server when waiting for an IP logon might be unwanted in your case but doesn't really look like a 'bug' from Novell to me. The general approach you choose looks not really sound to me - remote control for real business work was maybe promising in the early nineties, but has been replaced almost entirely by remote node or alternately Citrix/Terminal Server like connections.
The only workaround in your case seems removing IP between the workstation and the Novell server (so solely using it for the PCAnywhere and probably for Internet connectivity); with solely an IPX connection the logon screen probably will not cause server load.
And the more strategic solution is taking another route - seeing the presence of Novell in your setup probably not Citrix-like but remote node. Either with a hardware solution (like Shiva) or with the Novell remote node product. For most apps, works a lot faster than PC-Anywhere too...

Hope this helps,

<Erik> / The Netherlands

Collapse -

PCANYWHERE TCP/IP SERVER UTILIZATION

by EPAIT In reply to PCANYWHERE TCP/IP SERVER ...

Poster rated this answer

Collapse -

PCANYWHERE TCP/IP SERVER UTILIZATION

by scatco In reply to PCANYWHERE TCP/IP SERVER ...

Our Netware 5.1 Server utilization never got that high, but when I added an additional Server NIC, splitting IPX on one card and IP on the other card, performance improved. The workstations still bind both, however.

My hosts are never logged into the network (whether Network or Dial-up) and I have to make absolutely sure that the user has not set the default Windows Printer to a Network Printer or the Novell Login tries to connect to the server, even if I have modified the registry to set autologon=off. You can get the registry changes from Symantec Knowledgebase.

Is the high utilization causing any other problems with other workstations? I have had DOS programs cause high utilization, especially when copying or replicating large files.

Collapse -

PCANYWHERE TCP/IP SERVER UTILIZATION

by EPAIT In reply to PCANYWHERE TCP/IP SERVER ...

Thanks for your help..

Collapse -

PCANYWHERE TCP/IP SERVER UTILIZATION

by EPAIT In reply to PCANYWHERE TCP/IP SERVER ...

This question was closed by the author

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums