Hi, I have a windows 2003 64 bits server, the firewall is off and I need to use the port 8063 but I am unable to reach it. I tested it locally with telnet and there is no connection. My network card permit all. Should you have any suggestions to enable the port? Should Windows 2003 64 bits changed his security policies vs 32 bits? Regards.

Not really directory services related but: Are you sure your service is listening on port 8063? What does the following command on this machine shows: netstat -ano | findstr /i 8063http://setspn.blogspot.com

What application are you trying to use? Make sure that application is running on this server. It is an application related configuration. Use netstat –a command on the server to make sure the application is listening on port 8063. Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX Blogs - http://blogs.sivarajan.com/ Articles - http://www.sivarajan.com/publications.html Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara This posting is provided AS IS with no warranties, and confers no rights.

I used the netstat command and the port is inactive. Thanks.

The application comes from Computer Associates. It was certified on this platform but the port should be active. On windows 2008 64 bits I have no problems to open the port and the application works fine, but in Windows 2003 64 bits I have the problem. Regards

you can use tcpview to find out on which port your process/service is active: http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx http://setspn.blogspot.com

Let me explain additional information. The program is an agent that should be installed remotely via the 8063 port and should be listening and reporting information via the same 8063 port. The agent has the 8063 port pre-configured. The tcpview is useful but until I can install the agent. Regards

So you are having problems pushing the agent to the Windows 2003 x64 OS? I'm pretty sure the pushing itself won't use port 8063. Would be some chicken-egg situation.http://setspn.blogspot.com

One of the windows 2008 x64 servers had the 8063 closed. I tried to install the agent unsuccessfully. Until I opened the 8063 in Windows 2008 x64 the agent was installed successfully. I believe that this change was the reason to install the agent, it was the only change factor. Regards

Sounds like an application issue. My recommendation is to contact the application vendor. Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX Blogs - http://blogs.sivarajan.com/ Articles - http://www.sivarajan.com/publications.html Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara This posting is provided AS IS with no warranties, and confers no rights.

But what you think that telnet didn't connect locally with 8063 port?

If application is not listening on port 8063, you won’t be able to connect it using Telnet. Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX Blogs - http://blogs.sivarajan.com/ Articles - http://www.sivarajan.com/publications.html Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara This posting is provided AS IS with no warranties, and confers no rights.

Santhosh, the application is not installed on the server. I have another windows 2008 x64 server and the agent is not installed yet but this server is capable to establish connection via telnet on 8063 port. I will try to use IPSec. Regards and thanks all!

Please post the Netstat –a output from both computers here. Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX Blogs - http://blogs.sivarajan.com/ Articles - http://www.sivarajan.com/publications.html Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara This posting is provided AS IS with no warranties, and confers no rights.

Santosh, thank you for your help: the output of netstat -a on 2 servers. Regards. X64 server: C:\Documents and Settings\user>netstat -a Active Connections Proto Local Address Foreign Address State TCP idc-moss-st-01:smtp idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:http idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:epmap idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:microsoft-ds idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:1051 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:1236 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:1244 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:1248 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:1311 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:ms-wbt-server idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:8088 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:8089 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:12345 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:56737 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:56738 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:1092 idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:netbios-ssn idc-moss-st-01.mynet.com:0 LISTENING TCP idc-moss-st-01:1622 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:1653 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:1676 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2055 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2208 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2380 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2401 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2402 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-moss-st-01:2403 a184-50-249-83.deploy.akamaitechnologies.com:htt ps CLOSE_WAIT TCP idc-moss-st-01:2411 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-moss-st-01:2412 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-moss-st-01:2413 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-moss-st-01:2414 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-moss-st-01:2434 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2459 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2481 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2482 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2483 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:ms-v-worlds IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2566 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2569 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2570 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2571 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2572 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2574 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2575 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2576 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2577 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2578 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2579 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2580 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2581 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2582 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2583 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2584 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2585 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2586 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2587 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2588 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2589 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2590 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2591 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2592 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2593 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2594 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2598 HDQ-DC-01:epmap TIME_WAIT TCP idc-moss-st-01:2599 HDQ-DC-01:1026 TIME_WAIT TCP idc-moss-st-01:2600 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2601 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2602 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2603 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2604 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2605 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2606 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2607 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2608 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2609 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2610 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2611 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2612 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2613 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2614 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2615 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2616 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2617 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2618 IDC-MOSS-SQL-01:ms-sql-s TIME_WAIT TCP idc-moss-st-01:2622 HDQ-DC-01:microsoft-ds TIME_WAIT TCP idc-moss-st-01:2627 HDQ-DC-01:1026 ESTABLISHED TCP idc-moss-st-01:2630 HDQ-DC-01:ldap TIME_WAIT TCP idc-moss-st-01:2631 HDQ-DC-01:ldap TIME_WAIT TCP idc-moss-st-01:2633 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:2637 HDQ-DC-01:ldap TIME_WAIT TCP idc-moss-st-01:2638 HDQ-DC-01:microsoft-ds TIME_WAIT TCP idc-moss-st-01:2640 HDQ-DC-01:epmap ESTABLISHED TCP idc-moss-st-01:2641 HDQ-DC-01:1026 ESTABLISHED TCP idc-moss-st-01:2642 HDQ-DC-01:ldap TIME_WAIT TCP idc-moss-st-01:2643 HDQ-DC-01:ldap TIME_WAIT TCP idc-moss-st-01:2849 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:ms-wbt-server HDQITPRO04:51754 ESTABLISHED TCP idc-moss-st-01:3733 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:3800 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:3826 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED TCP idc-moss-st-01:4034 IDC-MOSS-SQL-01:ms-sql-s ESTABLISHED UDP idc-moss-st-01:snmp *:* UDP idc-moss-st-01:microsoft-ds *:* UDP idc-moss-st-01:isakmp *:* UDP idc-moss-st-01:3456 *:* UDP idc-moss-st-01:ipsec-msft *:* UDP idc-moss-st-01:ntp *:* UDP idc-moss-st-01:1025 *:* UDP idc-moss-st-01:1031 *:* UDP idc-moss-st-01:1047 *:* UDP idc-moss-st-01:1073 *:* UDP idc-moss-st-01:1093 *:* UDP idc-moss-st-01:2007 *:* UDP idc-moss-st-01:2514 *:* UDP idc-moss-st-01:2629 *:* UDP idc-moss-st-01:3456 *:* UDP idc-moss-st-01:ntp *:* UDP idc-moss-st-01:netbios-ns *:* UDP idc-moss-st-01:netbios-dgm *:* UDP idc-moss-st-01:ntp *:* 32 bits server (the agent was successfully installed and is listening on 8063 port): C:\Documents and Settings\user>netstat -a Active Connections Proto Local Address Foreign Address State TCP idc-wse-01:smtp idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:http idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:epmap idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:microsoft-ds idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1025 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1027 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1035 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1037 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1311 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1555 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1557 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1561 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:msmq idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:2103 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:2105 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:2107 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:3372 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:ms-wbt-server idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:8000 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:8063 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:8080 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:8888 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:12345 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1059 idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:netbios-ssn idc-wse-01.mynet.com:0 LISTENING TCP idc-wse-01:1026 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-wse-01:1028 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-wse-01:1029 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-wse-01:1030 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-wse-01:1031 a184-50-249-83.deploy.akamaitechnologies.com:htt ps ESTABLISHED TCP idc-wse-01:1033 HDQ-DC-01:epmap TIME_WAIT TCP idc-wse-01:activesync HDQ-DC-01:1026 TIME_WAIT TCP idc-wse-01:1043 HDQ-DC-01:microsoft-ds TIME_WAIT TCP idc-wse-01:1047 HDQ-DC-01:1026 ESTABLISHED TCP idc-wse-01:1049 HDQ-DC-01:microsoft-ds TIME_WAIT TCP idc-wse-01:1053 HDQ-DC-01:ldap TIME_WAIT TCP idc-wse-01:1054 HDQ-DC-01:ldap TIME_WAIT TCP idc-wse-01:1060 HDQ-DC-01:ldap TIME_WAIT TCP idc-wse-01:1061 HDQ-DC-01:microsoft-ds TIME_WAIT TCP idc-wse-01:1063 HDQ-DC-01:epmap ESTABLISHED TCP idc-wse-01:1064 HDQ-DC-01:1026 ESTABLISHED TCP idc-wse-01:1065 HDQ-DC-01:ldap TIME_WAIT TCP idc-wse-01:1066 HDQ-DC-01:ldap TIME_WAIT TCP idc-wse-01:1067 HDQ-DC-01:epmap ESTABLISHED TCP idc-wse-01:1071 HDQ-DC-01:netbios-ssn TIME_WAIT TCP idc-wse-01:ms-wbt-server HDQITPRO04:51768 ESTABLISHED TCP idc-wse-01:4985 a96-7-241-83.deploy.akamaitechnologies.com:https CLOSE_WAIT UDP idc-wse-01:snmp *:* UDP idc-wse-01:microsoft-ds *:* UDP idc-wse-01:isakmp *:* UDP idc-wse-01:1034 *:* UDP idc-wse-01:3456 *:* UDP idc-wse-01:3527 *:* UDP idc-wse-01:ipsec-msft *:* UDP idc-wse-01:ntp *:* UDP idc-wse-01:1041 *:* UDP idc-wse-01:1051 *:* UDP idc-wse-01:1062 *:* UDP idc-wse-01:1089 *:* UDP idc-wse-01:1119 *:* UDP idc-wse-01:1133 *:* UDP idc-wse-01:1474 *:* UDP idc-wse-01:3456 *:* UDP idc-wse-01:ntp *:* UDP idc-wse-01:netbios-ns *:* UDP idc-wse-01:netbios-dgm *:*

Yes. On your 32 bit server, application is listening on port 8063. Application is not running/listening on 64 bit server. TCP idc-wse-01:8063 idc-wse-01.mynet.com:0 LISTENING It sounds like an application issue. Make sure this application supports 64 bit server and contact your application vendor. Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX Blogs - http://blogs.sivarajan.com/ Articles - http://www.sivarajan.com/publications.html Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara This posting is provided AS IS with no warranties, and confers no rights.