* Winpak - Client Can not connect to server *

[Leo]

* Winpak - Client Can not connect to server *


1) Run Registry patch - XP sp2 and sp3 need to have this add to the registry on both the client and server:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\RPC]
"RestrictRemoteClients"=dword:00000000


2) Ping it. Ping the IP and ping the Name, just because you can ping the name does NOT mean the name will work OK. you need to telneed the name.

3) Telnet - If you can not telnet in from the client it not the client software, USE the IP ADDRESS & PC Name
From a Command prompt type:
Telnet ServerName 5555
Telnet ServerName 5556
If the screen goes blank it connected to the Database Server.
If the screen displays Waiting to connect then fails, Check the servers Firewall (turn it off)


4) Within the System Manager program change from Domain -> Workgroups.
When logging into a PC I would look to see if I had an option to (login to This computer). If I did I assumed it was a Domain(not true) I need to set it up as a Workgroup.

5) netstat
From a Command prompt type:
netstat -an
Not sure what you should be looking for, but tech support had me do it.

[Clemink]

We have old PC with win-pak 2 release 3.
Now we have to relocate win-pak server to other machine. I have install MSDE and win-pak 2 to new machine.
I've restored database from old PC, changed lan settings in SystemManager. The new machine has the same name and the same IP address like at old. Old PC disconnected from lan.
And i had a problem with starting win-pak client. Error is:
"Failed connect to:
Communications Server: comserv (<ip-address>)
Muster Server: (<ip-address>)"

Then i've tried your instructions. Checked all of these things and added your file to registry (cause new machine has XP SP2).
And now i have other problem.
When i'm trying to connect "Communications Server" service crashing. And win-pak tells me: Lost connection with Communication Server (<ip-address>).

I've listed a journal and saw an error "1000" with module "mfc42.dll, version 6.2.4131.0, address 0x000b8c72".

Can you help me with that? Thank you. And sorry for my bad english.

[Clemink]

Hmm. I found ..a solution.

Steps:
1) Dissconect COM1 cable (controller).
2) Run WIN-PAK 2 (we see errors at Events about finding our panels and doors)
3) Connect COM1 cable.

And win-pak can see our panels now. All system are working.
And service "Communication Server" would not shut down.

[Leo]

A lot of the problems is DNS or using Computer names and not IP addresses.

use Telnet to help find the problem
C:\telnet name/ip port - if screen goes blank it connected, if fails NO good.
C:\telnet ServerName 5555
C:\telnet 192.168.1.200 5555

ports:
db server-5555
achrive server-5556
Comm server-5566,5567,5568

[Leo]

I am at a site that is a DOMAIN so within System Manager -> RCP I used Domain, WOULD NOT WORK

Used Workgroups on Both computers, Restarted both.

JUST Works.
So from here out, it's alway Workgroups