P
Paul Green
I have a notebook computer with Windows XP that has a built-in wireless
802.11b connection (LAN-Express). It works fine, connecting to a network
through both the built-in Ethernet connection and the wireless. No problem.
The problem is when I attempt to install SSH's Sentinel 1.3 in order to use
my office's VPN (through a Linksys VPN router). With the Sentinel client
installed, the Wireless connection malfunctions. Although it can still
connect to the local network, it will not pick up the correct IP address
from the DHCP server (using instead a 169.254.x.x address).
The ethernet connection, however, continues to function just fine. Only the
wireless connection is problem. The ethernet continues to connect fine,
and retrieves a proper IP address. Oddly, even the wireless connection
still connects to the local Novell and Microsoft network. Even more oddly,
it cannot "ping" anything on the network, even those things it connects to.
I might have thought it was connecting through IPX, except that since it is
wireless, it should not be able to use IPX.
I have tried various TCP/IP stack repairs, but to no avial. Besides, since
it works on the wired network, there does not seem to be a problem with it
anyway. Also, I have another computer with a similar configuration, albeit
with a different internal wireless network adapter (an
Orinoco/Agere/Lucent), and it does not have a problem.
Also, if I delete the wireless connection and re-add it (filling in all the
WEP stuff, etc.), it will work until I reboot. Then I am back to square
one. I even tried to disable various aspects of the Sentinel client, but
nothing short of a complete uninstall seems to have any effect.
Help!
802.11b connection (LAN-Express). It works fine, connecting to a network
through both the built-in Ethernet connection and the wireless. No problem.
The problem is when I attempt to install SSH's Sentinel 1.3 in order to use
my office's VPN (through a Linksys VPN router). With the Sentinel client
installed, the Wireless connection malfunctions. Although it can still
connect to the local network, it will not pick up the correct IP address
from the DHCP server (using instead a 169.254.x.x address).
The ethernet connection, however, continues to function just fine. Only the
wireless connection is problem. The ethernet continues to connect fine,
and retrieves a proper IP address. Oddly, even the wireless connection
still connects to the local Novell and Microsoft network. Even more oddly,
it cannot "ping" anything on the network, even those things it connects to.
I might have thought it was connecting through IPX, except that since it is
wireless, it should not be able to use IPX.
I have tried various TCP/IP stack repairs, but to no avial. Besides, since
it works on the wired network, there does not seem to be a problem with it
anyway. Also, I have another computer with a similar configuration, albeit
with a different internal wireless network adapter (an
Orinoco/Agere/Lucent), and it does not have a problem.
Also, if I delete the wireless connection and re-add it (filling in all the
WEP stuff, etc.), it will work until I reboot. Then I am back to square
one. I even tried to disable various aspects of the Sentinel client, but
nothing short of a complete uninstall seems to have any effect.
Help!