Unable to ping from defined AE to verify the connection
Dear all,
Thank you very much for reading my posting.
So far, I have been installing Pacsone on 3 systems. Everything seems up and running.
For the first system, at the very beginning. I also had a problem with the Ping to verify the connnection. the remote AE is the LOCALHOST... Later I found out that if I do NOT define at least on AE in the AE table that have the same name as the AE title as I log in, I can NOT ping. This server is a WORKGROUP.
On the second system. I have everything up and running... Task Manager shows PacsOneSvr.exe is running. Port 1234 is used. AE with the same name as the AT title is created but I can't PING. this is a domain controller server. Because I run out of servers, so I have to install on this server.
On the third system which is the cluster nodes (2 nodes). I can make pacsone failover on both nodes (Imaging isn't it)... But both can't ping either.. These two nodes join the domain from the second system above.
All the remote AEs are the localhosts.
I wonder if PacsOne may not like the Domain or something.
Please help if you have seen this problem before.
Tom Tran
Thank you very much for reading my posting.
So far, I have been installing Pacsone on 3 systems. Everything seems up and running.
For the first system, at the very beginning. I also had a problem with the Ping to verify the connnection. the remote AE is the LOCALHOST... Later I found out that if I do NOT define at least on AE in the AE table that have the same name as the AE title as I log in, I can NOT ping. This server is a WORKGROUP.
On the second system. I have everything up and running... Task Manager shows PacsOneSvr.exe is running. Port 1234 is used. AE with the same name as the AT title is created but I can't PING. this is a domain controller server. Because I run out of servers, so I have to install on this server.
On the third system which is the cluster nodes (2 nodes). I can make pacsone failover on both nodes (Imaging isn't it)... But both can't ping either.. These two nodes join the domain from the second system above.
All the remote AEs are the localhosts.
I wonder if PacsOne may not like the Domain or something.
Please help if you have seen this problem before.
Tom Tran
Ok, we'll need more elaboration on your configurations and where ping failed:
1. Server 1:
What's the AE title you assigned for this server? IP address? Port number?
2. Server 2:
What's the AE title you assigned for this server? IP address? Port number?
3. Server 3:
Server 1:
What's the AE title you assigned for this server? IP address? Port number?
And ping failed when you tried to ping from which AE to which AE?
1. Server 1:
What's the AE title you assigned for this server? IP address? Port number?
2. Server 2:
What's the AE title you assigned for this server? IP address? Port number?
3. Server 3:
Server 1:
What's the AE title you assigned for this server? IP address? Port number?
And ping failed when you tried to ping from which AE to which AE?
Dear Pacsone Admin,
Here are the configuration:
On the tool bar: I click on Applicaton Entities:
then I see the following:
Current PacsOne Server Configurations:
Application Entity Title: PacsOne
Hostname: 123.123.123.123
TCP Port Number: 1234.
Then I click on Add to define a new AE.
Since I used iSCSI, so I have extra disk space to store DICOM files, so, everything is local. I enter the following for the new AE:
AE Title: PacsOne
Host name: locahost
IP: 127.0.0.1
Port:1234
Archive directory: G:/dicomdir
I also edit the host file and enter the host name and real IP and put real host name instead of localhost and real IP instead of 127.0.0.1.
OH, for first & second system, I did not use iscsi.. I used local C drive.
the error is:
fsockopen() failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)
thanks,
Tom
Here are the configuration:
On the tool bar: I click on Applicaton Entities:
then I see the following:
Current PacsOne Server Configurations:
Application Entity Title: PacsOne
Hostname: 123.123.123.123
TCP Port Number: 1234.
Then I click on Add to define a new AE.
Since I used iSCSI, so I have extra disk space to store DICOM files, so, everything is local. I enter the following for the new AE:
AE Title: PacsOne
Host name: locahost
IP: 127.0.0.1
Port:1234
Archive directory: G:/dicomdir
I also edit the host file and enter the host name and real IP and put real host name instead of localhost and real IP instead of 127.0.0.1.
OH, for first & second system, I did not use iscsi.. I used local C drive.
the error is:
fsockopen() failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)
thanks,
Tom
You still have not provided your configurations, so let's try another way:
Say you've logged in to server A, and tried to ping AE title B but failed, so we'd need the following information from you:
1. How's AE Title B defined in the Application Entity page of server A?
What's the AE Title, hostname, IP address, and port number you defined for this AE Title B?
Say you've logged in to server A, and tried to ping AE title B but failed, so we'd need the following information from you:
1. How's AE Title B defined in the Application Entity page of server A?
What's the AE Title, hostname, IP address, and port number you defined for this AE Title B?
Dear Pacsone Admin,
OK, let talk about one system now:
Everything is configured on one server.
mysql, php, apache, Pacsone, dicomdir, AE also point to the local server.
When I lauch the IE, it also from the server (I tried remote also).
So, in the defined AE, I have localhost for name and 127.0.0.1 for IP and 1234 for port. I also try "node1" for host name and xxx.xxx.xxx.xxx for IP. and node1 and xxx.xxx.xxx.xxx are defined in the hosts file.
For now, everything is in local C drive but in the very near future, we will use iscsi for storage so, the DICOMDIR and mySQL will be moved to iSCSI drive but they should not affect. So, theoratically, we will not have remote AE define.
Please let me know if you need anything else.
Thanks,
Tom
OK, let talk about one system now:
Everything is configured on one server.
mysql, php, apache, Pacsone, dicomdir, AE also point to the local server.
When I lauch the IE, it also from the server (I tried remote also).
So, in the defined AE, I have localhost for name and 127.0.0.1 for IP and 1234 for port. I also try "node1" for host name and xxx.xxx.xxx.xxx for IP. and node1 and xxx.xxx.xxx.xxx are defined in the hosts file.
For now, everything is in local C drive but in the very near future, we will use iscsi for storage so, the DICOMDIR and mySQL will be moved to iSCSI drive but they should not affect. So, theoratically, we will not have remote AE define.
Please let me know if you need anything else.
Thanks,
Tom
From what you've described here, it seems that you logged in server A, defined an AE named (???), IP address 127.0.0.1 and port 1234. Is that correct?
It doesn't matter what the hostname is used if you've specified an IP addr, so in the above example, the Ping link should work as long as there is an application listening on port 1234 on the same localhost.
The timeout error you got suggests there's no application listening to Port 1234 on the same localhost, so you need to check if PacsOne is really running by checking if you see both PacsOne.exe and PacsOneSrv.exe from the process list of the Windows Task Manager (CTL-ALT-DLT, Task Manager -> Process List). If not, then PacsOne is not running.
Another way to check if there's any application listening to Port 1234 is to run the netstat -aon -p tcp from a command shell, and see if you see a row like "0.0.0.0:1234" from the Local Address (second) column.
It doesn't matter what the hostname is used if you've specified an IP addr, so in the above example, the Ping link should work as long as there is an application listening on port 1234 on the same localhost.
The timeout error you got suggests there's no application listening to Port 1234 on the same localhost, so you need to check if PacsOne is really running by checking if you see both PacsOne.exe and PacsOneSrv.exe from the process list of the Windows Task Manager (CTL-ALT-DLT, Task Manager -> Process List). If not, then PacsOne is not running.
Another way to check if there's any application listening to Port 1234 is to run the netstat -aon -p tcp from a command shell, and see if you see a row like "0.0.0.0:1234" from the Local Address (second) column.
Dear PacsOne Admin,
Yes, it's correct. I log in Server A and define AE and ping Server A itself.
At the moment, I don't know how to set up and define remote AE yet.
I just checked both of my servers here is what I see:
This happens on both servers:
According to the services, "Pacsone Server Premium Edition" is running and the task manager only shows "PacsOneSvr.exe" process is running, not "PacsOne.exe"... Does it need both of the processes to run? if it does, why PacsOne.exe is not running.
Best regards,
Tom Tran
Yes, it's correct. I log in Server A and define AE and ping Server A itself.
At the moment, I don't know how to set up and define remote AE yet.
I just checked both of my servers here is what I see:
This happens on both servers:
According to the services, "Pacsone Server Premium Edition" is running and the task manager only shows "PacsOneSvr.exe" process is running, not "PacsOne.exe"... Does it need both of the processes to run? if it does, why PacsOne.exe is not running.
Best regards,
Tom Tran
This means your trial license is either missing or has expired.PacsOneNewBie wrote: According to the services, "Pacsone Server Premium Edition" is running and the task manager only shows "PacsOneSvr.exe" process is running, not "PacsOne.exe"... Does it need both of the processes to run? if it does, why PacsOne.exe is not running.
Did you by any chance uninstall PacsOne Server? If so, that'd explain why your trial license is missing, as it'll be removed by the uninstaller but will not be created again even if you reinstall PacsOne.
If you can find the trial license (license.dat under the directory where PacsOne is installed), you can send it to mailto:pacsone@pacsone.net and we'll check it out. Otherwise if your trial license is missing, you'll need to send the hostname/computer name of the server where PacsOne is installed, before we can create a new trial license for you.