Discussion:
[ace-users] Re: Naming service fails to start with ip address 192.168.2.x
(too old to reply)
Douglas C. Schmidt
2004-07-01 03:55:35 UTC
Permalink
Hi Ed,
Tao 1.2
Ace 5.2
You are using an ANCIENT version of ACE+TAO. Therefore, the first
thing I recommend that you do is upgrade to TAO 1.4.1, which you can
download from

http://deuce.doc.wustl.edu/Download.html

Please try this out and see if the problem goes away.

Thanks,

Doug
Windows XP Pro
VC6 SP5
Pentium 4 3GHZ HyperThreading
Intel D865GBF motherboard
2 network adapters: Intel Pro/1000 CT (internal) and Intel Pro/1000 MT
"D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release\Naming_Service.ex
e
-ORBEndpoint iiop://192.168.2.1:9999 -ORBDottedDecimalAddresses 1
-ORBdebuglevel 10"
.. the naming service fails to start and gives me the following error"
"TAO (300|1204) Loaded default protocol <IIOP_Factory>
TAO (300|1204) created new ORB <>
TAO (300|1204) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (300|1204) IIOP_Acceptor::open_i cannot open acceptor in port
The requested address is not valid in its context.
TAO (300|1204) unable to open acceptor for <192.168.2.1:9999>: No such
file or directory
(300|1204) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 11 (endpoint initialization failure in
Acceptor Registry; EINVAL), completed = NO
Destroying ORB <>"
If I change the ip address from 192.168.2.x to 192.168.1.x, the naming
service starts fine.
I have used the same version of the naming service and TAO on Windows
2000 with different hardware and 2 network cards with no problems.
Anybody has any suggestions of what could cause this?
Ed
--
Dr. Douglas C. Schmidt, Professor TEL: (615) 343-8197
Electrical Engineering and Computer Science FAX: (615) 343-7440
Vanderbilt University WEB: www.cs.wustl.edu/~schmidt/
Nashville, TN 37203 NET: ***@vanderbilt.edu
ed
2004-07-01 18:18:29 UTC
Permalink
Hi Doug,
I downloaded TAO 1.4.1 and built the naming service. I get the same
error as before but with more info that I do not understand. Please
read the following which will show both network cards: 192.168.1.2
works and 192.168.2.1 does not!!!

IP CONFIG
=========
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
===================

RUN THE NAMING SERVICE ON 192.168.2.1 WHICH FAILS
=================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk

D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1780|1076) Loaded
default protocol <IIOP_Factory>
TAO (1780|1076) created new ORB <>
TAO (1780|1076) IIOP_Acceptor::open_i() trying to listen on port 9999


TAO (1780|1076) IIOP_Acceptor::open_i cannot open acceptor in port
range (9999,9
999)- : A request to send or receive data was disallowed because the
socket is n
ot connected and (when sending on a datagram socket using a sendto
call) no addr
ess was supplied.

TAO (1780|1076) unable to open acceptor for <192.168.2.1:9999>: No
such file or
directory
(1780|1076) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 49 (endpoint initialization failure in
Acceptor Regi
stry; low 7 bits of errno: 73 Unknown error), completed = NO

Failed to start the Naming Service.
====================================

RUN THE NAMING SERVICE ON 192.168.1.2 WHICH SUCCEEDS
====================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk

D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1408|232) Loaded d
efault protocol <IIOP_Factory>
TAO (1408|232) created new ORB <>
TAO (1408|232) IIOP_Acceptor::open_i() trying to listen on port 9999

TAO (1408|232) IIOP_Acceptor::open_i - listening on:
<192.168.1.2:9999>
Notifying ImR of startup

We'll become a NameService
Missing ImR IOR, will not use the ImR
TAO (1408|232) - ORB_Core::run, start [run]
TAO (1408|232) - ORB_Core::run, calling handle_events()
===================

Options to the NS are: -ORBEndpoint iiop://192.168.2.1:9999
-ORBDottedDecimalAddresses 1 -ORBdebuglevel 10

Any ideas of what could cause this?

Regards,
Ed
Post by Douglas C. Schmidt
Hi Ed,
Tao 1.2
Ace 5.2
You are using an ANCIENT version of ACE+TAO. Therefore, the first
thing I recommend that you do is upgrade to TAO 1.4.1, which you can
download from
http://deuce.doc.wustl.edu/Download.html
Please try this out and see if the problem goes away.
Thanks,
Doug
Windows XP Pro
VC6 SP5
Pentium 4 3GHZ HyperThreading
Intel D865GBF motherboard
2 network adapters: Intel Pro/1000 CT (internal) and Intel Pro/1000 MT
"D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release\Naming_Service.ex
e
-ORBEndpoint iiop://192.168.2.1:9999 -ORBDottedDecimalAddresses 1
-ORBdebuglevel 10"
.. the naming service fails to start and gives me the following error"
"TAO (300|1204) Loaded default protocol <IIOP_Factory>
TAO (300|1204) created new ORB <>
TAO (300|1204) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (300|1204) IIOP_Acceptor::open_i cannot open acceptor in port
The requested address is not valid in its context.
TAO (300|1204) unable to open acceptor for <192.168.2.1:9999>: No such
file or directory
(300|1204) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 11 (endpoint initialization failure in
Acceptor Registry; EINVAL), completed = NO
Destroying ORB <>"
If I change the ip address from 192.168.2.x to 192.168.1.x, the naming
service starts fine.
I have used the same version of the naming service and TAO on Windows
2000 with different hardware and 2 network cards with no problems.
Anybody has any suggestions of what could cause this?
Ed
ed
2004-07-01 22:27:35 UTC
Permalink
Hi Doug,
After some experimentation, I found that the Microsoft Proxy Client
2.0 caused this behavior! (do not know why, but it is an old program)
Uninstalling it fixed the problem.
Thanks and Regards,
Ed
Post by ed
Hi Doug,
I downloaded TAO 1.4.1 and built the naming service. I get the same
error as before but with more info that I do not understand. Please
read the following which will show both network cards: 192.168.1.2
works and 192.168.2.1 does not!!!
IP CONFIG
=========
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ipconfig
Windows IP Configuration
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
===================
RUN THE NAMING SERVICE ON 192.168.2.1 WHICH FAILS
=================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1780|1076) Loaded
default protocol <IIOP_Factory>
TAO (1780|1076) created new ORB <>
TAO (1780|1076) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (1780|1076) IIOP_Acceptor::open_i cannot open acceptor in port
range (9999,9
999)- : A request to send or receive data was disallowed because the
socket is n
ot connected and (when sending on a datagram socket using a sendto
call) no addr
ess was supplied.
TAO (1780|1076) unable to open acceptor for <192.168.2.1:9999>: No
such file or
directory
(1780|1076) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 49 (endpoint initialization failure in
Acceptor Regi
stry; low 7 bits of errno: 73 Unknown error), completed = NO
Failed to start the Naming Service.
====================================
RUN THE NAMING SERVICE ON 192.168.1.2 WHICH SUCCEEDS
====================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1408|232) Loaded d
efault protocol <IIOP_Factory>
TAO (1408|232) created new ORB <>
TAO (1408|232) IIOP_Acceptor::open_i() trying to listen on port 9999
<192.168.1.2:9999>
Notifying ImR of startup
We'll become a NameService
Missing ImR IOR, will not use the ImR
TAO (1408|232) - ORB_Core::run, start [run]
TAO (1408|232) - ORB_Core::run, calling handle_events()
===================
Options to the NS are: -ORBEndpoint iiop://192.168.2.1:9999
-ORBDottedDecimalAddresses 1 -ORBdebuglevel 10
Any ideas of what could cause this?
Regards,
Ed
Post by Douglas C. Schmidt
Hi Ed,
Tao 1.2
Ace 5.2
You are using an ANCIENT version of ACE+TAO. Therefore, the first
thing I recommend that you do is upgrade to TAO 1.4.1, which you can
download from
http://deuce.doc.wustl.edu/Download.html
Please try this out and see if the problem goes away.
Thanks,
Doug
Windows XP Pro
VC6 SP5
Pentium 4 3GHZ HyperThreading
Intel D865GBF motherboard
2 network adapters: Intel Pro/1000 CT (internal) and Intel Pro/1000 MT
"D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release\Naming_Service.ex
e
-ORBEndpoint iiop://192.168.2.1:9999 -ORBDottedDecimalAddresses 1
-ORBdebuglevel 10"
.. the naming service fails to start and gives me the following error"
"TAO (300|1204) Loaded default protocol <IIOP_Factory>
TAO (300|1204) created new ORB <>
TAO (300|1204) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (300|1204) IIOP_Acceptor::open_i cannot open acceptor in port
The requested address is not valid in its context.
TAO (300|1204) unable to open acceptor for <192.168.2.1:9999>: No such
file or directory
(300|1204) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 11 (endpoint initialization failure in
Acceptor Registry; EINVAL), completed = NO
Destroying ORB <>"
If I change the ip address from 192.168.2.x to 192.168.1.x, the naming
service starts fine.
I have used the same version of the naming service and TAO on Windows
2000 with different hardware and 2 network cards with no problems.
Anybody has any suggestions of what could cause this?
Ed
ed
2004-07-01 22:28:37 UTC
Permalink
Hi Doug,
After some experimentation, I found that the Microsoft Proxy Client
2.0 caused this behavior! (do not know why, but it is an old program)
Uninstalling it fixed the problem.
Thanks and Regards,
Ed
Post by ed
Hi Doug,
I downloaded TAO 1.4.1 and built the naming service. I get the same
error as before but with more info that I do not understand. Please
read the following which will show both network cards: 192.168.1.2
works and 192.168.2.1 does not!!!
IP CONFIG
=========
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ipconfig
Windows IP Configuration
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
===================
RUN THE NAMING SERVICE ON 192.168.2.1 WHICH FAILS
=================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1780|1076) Loaded
default protocol <IIOP_Factory>
TAO (1780|1076) created new ORB <>
TAO (1780|1076) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (1780|1076) IIOP_Acceptor::open_i cannot open acceptor in port
range (9999,9
999)- : A request to send or receive data was disallowed because the
socket is n
ot connected and (when sending on a datagram socket using a sendto
call) no addr
ess was supplied.
TAO (1780|1076) unable to open acceptor for <192.168.2.1:9999>: No
such file or
directory
(1780|1076) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 49 (endpoint initialization failure in
Acceptor Regi
stry; low 7 bits of errno: 73 Unknown error), completed = NO
Failed to start the Naming Service.
====================================
RUN THE NAMING SERVICE ON 192.168.1.2 WHICH SUCCEEDS
====================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1408|232) Loaded d
efault protocol <IIOP_Factory>
TAO (1408|232) created new ORB <>
TAO (1408|232) IIOP_Acceptor::open_i() trying to listen on port 9999
<192.168.1.2:9999>
Notifying ImR of startup
We'll become a NameService
Missing ImR IOR, will not use the ImR
TAO (1408|232) - ORB_Core::run, start [run]
TAO (1408|232) - ORB_Core::run, calling handle_events()
===================
Options to the NS are: -ORBEndpoint iiop://192.168.2.1:9999
-ORBDottedDecimalAddresses 1 -ORBdebuglevel 10
Any ideas of what could cause this?
Regards,
Ed
Post by Douglas C. Schmidt
Hi Ed,
Tao 1.2
Ace 5.2
You are using an ANCIENT version of ACE+TAO. Therefore, the first
thing I recommend that you do is upgrade to TAO 1.4.1, which you can
download from
http://deuce.doc.wustl.edu/Download.html
Please try this out and see if the problem goes away.
Thanks,
Doug
Windows XP Pro
VC6 SP5
Pentium 4 3GHZ HyperThreading
Intel D865GBF motherboard
2 network adapters: Intel Pro/1000 CT (internal) and Intel Pro/1000 MT
"D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release\Naming_Service.ex
e
-ORBEndpoint iiop://192.168.2.1:9999 -ORBDottedDecimalAddresses 1
-ORBdebuglevel 10"
.. the naming service fails to start and gives me the following error"
"TAO (300|1204) Loaded default protocol <IIOP_Factory>
TAO (300|1204) created new ORB <>
TAO (300|1204) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (300|1204) IIOP_Acceptor::open_i cannot open acceptor in port
The requested address is not valid in its context.
TAO (300|1204) unable to open acceptor for <192.168.2.1:9999>: No such
file or directory
(300|1204) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 11 (endpoint initialization failure in
Acceptor Registry; EINVAL), completed = NO
Destroying ORB <>"
If I change the ip address from 192.168.2.x to 192.168.1.x, the naming
service starts fine.
I have used the same version of the naming service and TAO on Windows
2000 with different hardware and 2 network cards with no problems.
Anybody has any suggestions of what could cause this?
Ed
ed
2004-07-01 22:31:14 UTC
Permalink
Hi Doug,
After some experimentation, I found that the Microsoft Proxy Client
2.0 caused this behavior! (do not know why, but it is an old program)
Uninstalling it fixed the problem.
Thanks and Regards,
Ed
Post by ed
Hi Doug,
I downloaded TAO 1.4.1 and built the naming service. I get the same
error as before but with more info that I do not understand. Please
read the following which will show both network cards: 192.168.1.2
works and 192.168.2.1 does not!!!
IP CONFIG
=========
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ipconfig
Windows IP Configuration
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
===================
RUN THE NAMING SERVICE ON 192.168.2.1 WHICH FAILS
=================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1780|1076) Loaded
default protocol <IIOP_Factory>
TAO (1780|1076) created new ORB <>
TAO (1780|1076) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (1780|1076) IIOP_Acceptor::open_i cannot open acceptor in port
range (9999,9
999)- : A request to send or receive data was disallowed because the
socket is n
ot connected and (when sending on a datagram socket using a sendto
call) no addr
ess was supplied.
TAO (1780|1076) unable to open acceptor for <192.168.2.1:9999>: No
such file or
directory
(1780|1076) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 49 (endpoint initialization failure in
Acceptor Regi
stry; low 7 bits of errno: 73 Unknown error), completed = NO
Failed to start the Naming Service.
====================================
RUN THE NAMING SERVICE ON 192.168.1.2 WHICH SUCCEEDS
====================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1408|232) Loaded d
efault protocol <IIOP_Factory>
TAO (1408|232) created new ORB <>
TAO (1408|232) IIOP_Acceptor::open_i() trying to listen on port 9999
<192.168.1.2:9999>
Notifying ImR of startup
We'll become a NameService
Missing ImR IOR, will not use the ImR
TAO (1408|232) - ORB_Core::run, start [run]
TAO (1408|232) - ORB_Core::run, calling handle_events()
===================
Options to the NS are: -ORBEndpoint iiop://192.168.2.1:9999
-ORBDottedDecimalAddresses 1 -ORBdebuglevel 10
Any ideas of what could cause this?
Regards,
Ed
Post by Douglas C. Schmidt
Hi Ed,
Tao 1.2
Ace 5.2
You are using an ANCIENT version of ACE+TAO. Therefore, the first
thing I recommend that you do is upgrade to TAO 1.4.1, which you can
download from
http://deuce.doc.wustl.edu/Download.html
Please try this out and see if the problem goes away.
Thanks,
Doug
Windows XP Pro
VC6 SP5
Pentium 4 3GHZ HyperThreading
Intel D865GBF motherboard
2 network adapters: Intel Pro/1000 CT (internal) and Intel Pro/1000 MT
"D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release\Naming_Service.ex
e
-ORBEndpoint iiop://192.168.2.1:9999 -ORBDottedDecimalAddresses 1
-ORBdebuglevel 10"
.. the naming service fails to start and gives me the following error"
"TAO (300|1204) Loaded default protocol <IIOP_Factory>
TAO (300|1204) created new ORB <>
TAO (300|1204) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (300|1204) IIOP_Acceptor::open_i cannot open acceptor in port
The requested address is not valid in its context.
TAO (300|1204) unable to open acceptor for <192.168.2.1:9999>: No such
file or directory
(300|1204) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 11 (endpoint initialization failure in
Acceptor Registry; EINVAL), completed = NO
Destroying ORB <>"
If I change the ip address from 192.168.2.x to 192.168.1.x, the naming
service starts fine.
I have used the same version of the naming service and TAO on Windows
2000 with different hardware and 2 network cards with no problems.
Anybody has any suggestions of what could cause this?
Ed
ed
2004-07-01 23:04:15 UTC
Permalink
Doug,

Before spending too much time on this... After some experimentation, I
found that the Microsoft Proxy Client 2.0 was causing this behavior.
(Do not know why! But it is an old program) After uninstalling it,
everything was OK.

Regards,
Ed
Post by ed
Hi Doug,
I downloaded TAO 1.4.1 and built the naming service. I get the same
error as before but with more info that I do not understand. Please
read the following which will show both network cards: 192.168.1.2
works and 192.168.2.1 does not!!!
IP CONFIG
=========
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ipconfig
Windows IP Configuration
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
===================
RUN THE NAMING SERVICE ON 192.168.2.1 WHICH FAILS
=================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1780|1076) Loaded
default protocol <IIOP_Factory>
TAO (1780|1076) created new ORB <>
TAO (1780|1076) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (1780|1076) IIOP_Acceptor::open_i cannot open acceptor in port
range (9999,9
999)- : A request to send or receive data was disallowed because the
socket is n
ot connected and (when sending on a datagram socket using a sendto
call) no addr
ess was supplied.
TAO (1780|1076) unable to open acceptor for <192.168.2.1:9999>: No
such file or
directory
(1780|1076) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 49 (endpoint initialization failure in
Acceptor Regi
stry; low 7 bits of errno: 73 Unknown error), completed = NO
Failed to start the Naming Service.
====================================
RUN THE NAMING SERVICE ON 192.168.1.2 WHICH SUCCEEDS
====================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1408|232) Loaded d
efault protocol <IIOP_Factory>
TAO (1408|232) created new ORB <>
TAO (1408|232) IIOP_Acceptor::open_i() trying to listen on port 9999
<192.168.1.2:9999>
Notifying ImR of startup
We'll become a NameService
Missing ImR IOR, will not use the ImR
TAO (1408|232) - ORB_Core::run, start [run]
TAO (1408|232) - ORB_Core::run, calling handle_events()
===================
Options to the NS are: -ORBEndpoint iiop://192.168.2.1:9999
-ORBDottedDecimalAddresses 1 -ORBdebuglevel 10
Any ideas of what could cause this?
Regards,
Ed
Post by Douglas C. Schmidt
Hi Ed,
Tao 1.2
Ace 5.2
You are using an ANCIENT version of ACE+TAO. Therefore, the first
thing I recommend that you do is upgrade to TAO 1.4.1, which you can
download from
http://deuce.doc.wustl.edu/Download.html
Please try this out and see if the problem goes away.
Thanks,
Doug
Windows XP Pro
VC6 SP5
Pentium 4 3GHZ HyperThreading
Intel D865GBF motherboard
2 network adapters: Intel Pro/1000 CT (internal) and Intel Pro/1000 MT
"D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release\Naming_Service.ex
e
-ORBEndpoint iiop://192.168.2.1:9999 -ORBDottedDecimalAddresses 1
-ORBdebuglevel 10"
.. the naming service fails to start and gives me the following error"
"TAO (300|1204) Loaded default protocol <IIOP_Factory>
TAO (300|1204) created new ORB <>
TAO (300|1204) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (300|1204) IIOP_Acceptor::open_i cannot open acceptor in port
The requested address is not valid in its context.
TAO (300|1204) unable to open acceptor for <192.168.2.1:9999>: No such
file or directory
(300|1204) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 11 (endpoint initialization failure in
Acceptor Registry; EINVAL), completed = NO
Destroying ORB <>"
If I change the ip address from 192.168.2.x to 192.168.1.x, the naming
service starts fine.
I have used the same version of the naming service and TAO on Windows
2000 with different hardware and 2 network cards with no problems.
Anybody has any suggestions of what could cause this?
Ed
Douglas C. Schmidt
2004-07-02 01:46:02 UTC
Permalink
Hi Ed,
Post by ed
After some experimentation, I found that the Microsoft Proxy Client
2.0 caused this behavior! (do not know why, but it is an old program)
Uninstalling it fixed the problem.
Great, thanks for chasing this down - I wasn't sure what to advise you
;-)

take care,

Doug
Post by ed
Post by ed
Hi Doug,
I downloaded TAO 1.4.1 and built the naming service. I get the same
error as before but with more info that I do not understand. Please
read the following which will show both network cards: 192.168.1.2
works and 192.168.2.1 does not!!!
IP CONFIG
=========
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ipconfig
Windows IP Configuration
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
===================
RUN THE NAMING SERVICE ON 192.168.2.1 WHICH FAILS
=================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1780|1076) Loaded
default protocol <IIOP_Factory>
TAO (1780|1076) created new ORB <>
TAO (1780|1076) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (1780|1076) IIOP_Acceptor::open_i cannot open acceptor in port
range (9999,9
999)- : A request to send or receive data was disallowed because the
socket is n
ot connected and (when sending on a datagram socket using a sendto
call) no addr
ess was supplied.
TAO (1780|1076) unable to open acceptor for <192.168.2.1:9999>: No
such file or
directory
(1780|1076) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 49 (endpoint initialization failure in
Acceptor Regi
stry; low 7 bits of errno: 73 Unknown error), completed = NO
Failed to start the Naming Service.
====================================
RUN THE NAMING SERVICE ON 192.168.1.2 WHICH SUCCEEDS
====================================================
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>ns.lnk
D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release>TAO
(1408|232) Loaded d
efault protocol <IIOP_Factory>
TAO (1408|232) created new ORB <>
TAO (1408|232) IIOP_Acceptor::open_i() trying to listen on port 9999
<192.168.1.2:9999>
Notifying ImR of startup
We'll become a NameService
Missing ImR IOR, will not use the ImR
TAO (1408|232) - ORB_Core::run, start [run]
TAO (1408|232) - ORB_Core::run, calling handle_events()
===================
Options to the NS are: -ORBEndpoint iiop://192.168.2.1:9999
-ORBDottedDecimalAddresses 1 -ORBdebuglevel 10
Any ideas of what could cause this?
Regards,
Ed
Post by Douglas C. Schmidt
Hi Ed,
Tao 1.2
Ace 5.2
You are using an ANCIENT version of ACE+TAO. Therefore, the first
thing I recommend that you do is upgrade to TAO 1.4.1, which you can
download from
http://deuce.doc.wustl.edu/Download.html
Please try this out and see if the problem goes away.
Thanks,
Doug
Windows XP Pro
VC6 SP5
Pentium 4 3GHZ HyperThreading
Intel D865GBF motherboard
2 network adapters: Intel Pro/1000 CT (internal) and Intel Pro/1000 MT
"D:\Tools\ACE_wrappers\TAO\orbsvcs\Naming_Service\Release\Naming_Service.ex
e
-ORBEndpoint iiop://192.168.2.1:9999 -ORBDottedDecimalAddresses 1
-ORBdebuglevel 10"
.. the naming service fails to start and gives me the following error"
"TAO (300|1204) Loaded default protocol <IIOP_Factory>
TAO (300|1204) created new ORB <>
TAO (300|1204) IIOP_Acceptor::open_i() trying to listen on port 9999
TAO (300|1204) IIOP_Acceptor::open_i cannot open acceptor in port
The requested address is not valid in its context.
TAO (300|1204) unable to open acceptor for <192.168.2.1:9999>: No such
file or directory
(300|1204) EXCEPTION, TAO_Naming_Service::init
system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'
TAO exception, minor code = 11 (endpoint initialization failure in
Acceptor Registry; EINVAL), completed = NO
Destroying ORB <>"
If I change the ip address from 192.168.2.x to 192.168.1.x, the naming
service starts fine.
I have used the same version of the naming service and TAO on Windows
2000 with different hardware and 2 network cards with no problems.
Anybody has any suggestions of what could cause this?
Ed
--
Dr. Douglas C. Schmidt, Professor TEL: (615) 343-8197
Electrical Engineering and Computer Science FAX: (615) 343-7440
Vanderbilt University WEB: www.cs.wustl.edu/~schmidt/
Nashville, TN 37203 NET: ***@vanderbilt.edu
Continue reading on narkive:
Search results for '[ace-users] Re: Naming service fails to start with ip address 192.168.2.x' (Questions and Answers)
3
replies
what is DNS?what is Active Directory?what is patch file?
started 2006-10-10 03:15:22 UTC
computer networking
5
replies
can i get question answer of asp.net ?
started 2006-10-11 00:02:47 UTC
software
5
replies
i have a DNS error coming up?
started 2009-11-24 04:29:17 UTC
computer networking
6
replies
who win the match for jonh and randy ortan?
started 2007-08-19 06:00:21 UTC
rugby league
3
replies
Briefly describe the Microsoft's 2000 DNS management?
started 2006-08-17 22:05:37 UTC
computer networking
Loading...