Client browser fails with IPX-IP Gateway
Brian Moore
I have a Windows 98 client with Client32 v3.2 and running Internet
Explorer 5 that cannot connect to the Internet through BM2.1 running
on a NW4.11 server. After timing out, the browser returns an error
saying that the page could not be found. (DNS error perhaps?)
Prior to loading Client v3.2 the machine had Client v2.2 and COULD
connect to the Internet, though performance was very sluggish and
information in the IPX/IP Gateway window indicated the connection had
been established through a bindery connection rather than NDS.
The client PC is configured with IPX only. No Windows TCP/IP stack has
been installed.
Any thoughts about resolving this problem would be much appreciated!!
Brian Moore
CSL
you are getting all these problems because you can't use a client
version later than 2.2 with BM2.1. In addition to this, WIn98 natively
support winsock2, and this is incompatible with BM2.1
--
Cat
Novell Support Connection Volunteer
Craig Johnson
I do not think that IE5 will support the old IPX/IP Gateway. About the
only thing I can think of that might help here is to get a copy of the
MS wsock32.dll and put it in the same directory as the IE5 executable.
Cat may have more ideas on this since she supports IPX/IP gateway on a
daily basis and I don't.
Craig Johnson
Novell Support Connection SysOp
(See http://nscsysop.hypermart.net for a book on configuring
BorderManager packet filter exceptions)
Fokken
we had the same problems and as I can see it, a lot of other people do.
The problems even did not vanish after changing to BM 3.5. If one uses
Client 2.5 with BM 3.5 and IPX/IP Gateway everything is fine, but changing
to Client 3.x prevents most of our machines to connect to the gateway. The
few that did connect, unfortunately did not tell their secret, why they
do.
We tried really a lot of things, but nothing worked, so finally we changed
to IP/IP-Gateway .
If you really did find a way using IPX/IP-Gateway with 3.x-Clients (Win
98) and BM 3.x, please let us know.
Achim Fokken
Thomas Brewster
Bordermanager 3.0 and Client32 3.1. First remove the client32
software, install the TCP/IP protocol on the machine (even if you're
only going to run IPX on your network), and then reinstall the
client32. Make sure the Client32 IP gateway is installed and is points
to your bordermanager server. You can then remove TCP/IP from the
machine if you wish.
We have noticed that Netscape works fine, but Internet explorer is much
slower. Netscape will load a page in 30 seconds where Internet
Explorer will take about 90-120 seconds to load the same page. I've
read some theories that IE is more picky about making winsock2 calls,
and that accounts for the sluggishness. I'm looking at migrating away
from the IPX gateway to fix these problems.
* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
CSL
Hi Thomas,
> We have noticed that Netscape works fine, but Internet explorer is much
> slower. Netscape will load a page in 30 seconds where Internet
> Explorer will take about 90-120 seconds to load the same page. I've
> read some theories that IE is more picky about making winsock2 calls,
> and that accounts for the sluggishness. I'm looking at migrating away
> from the IPX gateway to fix these problems.
I had a call open with Novell (for more than 1 year) and MS about the performance with IE and the
IP/IPX gateway. MS never actually did anything other than pointing me to some technical documents in
their site (whose suggestion I tried already, and didn't work) while Novell tried to help a lot, but
they were never able to reproduce the problem.
The bad performance with IE is actually not between IE and the gateway, but between IE, the gateway
and the files in the proxy cache.
When I load files directly from the internet (i.e. they aren't in the cache) NS and IE have the same
performance.
If the file is in the BM cache it takes forever to come.
Novell at the end gave up, and issued a product defect.
Considering that the IPX/IP gateway is a "mature product" this means that this problem will never be
fixed.
Moving away from the ipx/ip gateway is the best choice.
Thomas Brewster
move away from the IPX/IP gateway.
phantom111
the 2.5,3.02 and 3.10 client versions. All are using the IPX to IP
gateway without a problem.
First, your clients are attaching in bindery mode, thus BorderManager
cannot manage there internet access. On the client, use the full
context name to the BM server in the IPX-to-IP gateway field. It must
begin with the leading period (.). This will ensure that your clients
receive an NDS connection to the BM server.
Second, I do not have any 3.2 clients, but it has been my experience
that when I needed to update a client version, that I must first run
UNC32.EXE (Of both the original client version and the newer client
version) before I could reinsatll the client and have it work correctly.
Steve DiMare
Northbridge Public Schools
jmerkesdal
We're using IPXIPgateway with NW5 SP4 on a Boardmanager installation.
and I'm just wondering what's the current status regarding this issue ?
Best regards
Joar Merkesdal
CSL
could you please tell me exactly what is your problem?
What version of the Client are you using? And what browser version?
Thanks
jmerkesdal
wrote:
Hi again
Here are some more information about the client and the connected server
PC:
NT 4.0 English, SP 6a
NW client 4.71 SP 2
Iexplorer 4.0 or higher
Server
NW 5 SP 4
NDS 7.45
Boarder Manger 3.5 SP1
My problem seem to be .....
I had a call open with Novell (for more than 1 year) and MS about the
performance with IE and the IP/IPX gateway. MS never actually did
anything other than pointing me to some technical documents in their
site (whose suggestion I tried already, and didn't work) while Novell
tried to help a lot, but they were never able to reproduce the problem.
The bad performance with IE is actually not between IE and the gateway,
but between IE, the gateway and the files in the proxy cache.
When I load files directly from the internet (i.e. they aren't in the
cache) NS and IE have the same performance.
If the file is in the BM cache it takes forever to come. Novell at the
end gave up, and issued a product defect. Considering that the IPX/IP
gateway is a "mature product" this means that this problem will never
be fixed.Moving away from the ipx/ip gateway is the best choice. --
Cat
Novell Support Connection Volunteer
....is this still so ??
If that's still the issue, what alternatives do I have if I need the
function IPXIPGatway presently are covering ??
We're using this function today in combination with IPX and IP
filtering in order to controll access to different subnets with various
resources.
Can IPXIPGateway be replaced with other sofware (framework - ichain ??)
from Novell to perform this operation ?
CSL
I see what you mean now.
you would be pleased to know that I went through EXACTLY the same problem.
Bed performance between IE and the proxy cache, novell incident, more than one year of waiting and
testing patches, and at the end: nothing (fun
(I also went through the useless MS support).
Yes, the situation is still the same. As far as I know, nothing changed.
> If that's still the issue, what alternatives do I have if I need the
> function IPXIPGatway presently are covering ??
Well, if you need to give access to w/s with IPX only the IPX/IP gateway is your only solution. My
recomandation is that you install the IP stack on your w/s and that you opt for a proxy/NAT and
packet filtering configuration.
this is what I did. I didn't loose any level of control. I would rather say that I added some
features to the logging and control of my system.
> We're using this function today in combination with IPX and IP
> filtering in order to controll access to different subnets with various
> resources.
From differnet subnets within your LAN or on the internet?
Depending on your configuration you can still do it or not. If all the traffic is routed through the
BM server you will still be able to apply packet filters.
You will loose access control based on NDS identities for services that do not use the proxies.
jmerkesdal
wrote:
> hi Joar,
> Unfortunately I am afraid that my answer doesn't change.
> No patches worked for me....I had to stick with NEtscape as
> browser and
> speed up my project to get away from the ipx/ip gateway....
> --
> Cat
> Novell Support Connection Volunteer
Hi again
On my way to do this I've looked into Socks v5.
ref: http://www.socks.nec.com/aboutsocks.html
Could the solution be as simple as that or is there a catch !?
BR
CSL
I am not sure what solution you are referring to.Use the SOCKS gateway?
to be able to use the SOCKS gateway you need IP on the clients...