E
Eric Hubert
Hello,
I am currently having some troubles with my software running on
a Windows XP workstation which includes 2 Ethernet cards, the
default one and a WIFI adapter (each of them being used).
I am running a client-server application developed in JAVA and
using Borland Visibroker with its Naming Service for communication.
Here is my problem: my server and the naming service run as a
Windows service to be available ASAP, before any user login.
When the naming service starts, it gets its local address (the
default one). When a client reaches the naming service through
WIFI network, the naming service sends a FORWARD message to
keep the client informed of its address, the default one. When
this is done, the client cannot reach the naming service any
more...
Have you already met this kind of problem?
Is there any way to force the WIFI to be the default Ethernet
card, or inhibit the default card at startup to be sure that
the naming service gets it address for the WIFI network?
Any other idea to resolve my problem?
A solution would be to get rid of the default Ethernet adapter,
but this would have a significative impact on the hardware
architecture and I would prefer not to change it for the
moment.
Many thanks for the reading of this message,
any feedback would be welcome.
Eric
I am currently having some troubles with my software running on
a Windows XP workstation which includes 2 Ethernet cards, the
default one and a WIFI adapter (each of them being used).
I am running a client-server application developed in JAVA and
using Borland Visibroker with its Naming Service for communication.
Here is my problem: my server and the naming service run as a
Windows service to be available ASAP, before any user login.
When the naming service starts, it gets its local address (the
default one). When a client reaches the naming service through
WIFI network, the naming service sends a FORWARD message to
keep the client informed of its address, the default one. When
this is done, the client cannot reach the naming service any
more...
Have you already met this kind of problem?
Is there any way to force the WIFI to be the default Ethernet
card, or inhibit the default card at startup to be sure that
the naming service gets it address for the WIFI network?
Any other idea to resolve my problem?
A solution would be to get rid of the default Ethernet adapter,
but this would have a significative impact on the hardware
architecture and I would prefer not to change it for the
moment.
Many thanks for the reading of this message,
any feedback would be welcome.
Eric