client 3.3 win98se "gateway not connected"
lbradford
nw4.11 nw4sp8a bmee3.5 bmsp1 win98se client32 v3.30
in the properties for the ip gateway on the client workstation under
"current gateway status" i see "gateway not connected".
the gateway is enabled with preferred server and preferred tree filled
in... any ideas?
thanks
l.bradford
* 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
as far as I know the client 3.3. hasn't been tested with the IP gateway
because th eIP gateway is a "mature" product, and no new releases are
tested for back compatibility. If you re using the gateway you should
stick to client 3.1.
Bythe way, are you using SSO authentication to the gateway? If that's
the case, you may try to backrev the version of Clntrust.exe and see if
it helps.
--
Cat
Novell Support Connection Volunteer
Fluxy
installed and I too cannot get the client3.3 to connect through the
Gateway. This happens on both 95 & 98SE.
I have to use client 3.3 due to a bug in both 3.1 & 3.2 which the
Novell support site recommended the update to 3.3 (bug is wm95sast
lockup during login).
Please help.
CSL
as I mentioned, the IP gateway will probably not work with the client
3.3. You should try to use the old Clntrust.exe, but I am not sure it
will solve your problem.
I recommend you ask Novell if you can add some files to 3.1 to fix the
bug you mentioned, or if you can backrev some files of the client 3.3 to
make the gateway work.
Frankly, the best suggesiton I can give you is to get away fromt he IP
gateway immediately. Start migating your users to IP. Note that you can
still use Ipx to communicate ot your servers, but you may want to add
the IP stach to your clients for the internet access.
Fluxy
work? Is there an updated gatway product that I am unaware of
(currently using BM3.5 SP1)?
I cannot get rid of the gateway at the moment for logistical problems,
but it is one which I am working towards. in the meantime I am having a
major headache with the current problem.
Who/how do I contact Novell in regards to adding extra files to client
3.1 or backreving client 3.3?
CSL
> Why is the gateway product included in the 3.3 client if it will not
> work? Is there an updated gatway product that I am unaware of
> (currently using BM3.5 SP1)?
well, you are right. We had a long discussiona about this with other sysops too, and we all agree
that Novell should still support the IP gateway with the new clients, at least as long as the IP
gateway is sold as part of BM.
Did you try to backrev only the clntrust.exe? It helped in other cases.
> Who/how do I contact Novell in regards to adding extra files to client
> 3.1 or backreving client 3.3?
I would say that you should open an incident with Novell. If this is a real bug (and it is, hold your
position!) they shouldn't charge anything for it.
Fluxy
the moment to resolve a problem where the gateway allows all users
access (depending on ACL rules) without the need for Clntrust.exe at
all. I did not even know that clntrust was needed until very recently,
and we have been using the product in various forms for 3 years.
I am reluctant to place a call with Novell technical support as last
time they took 4 weeks to answer my call only to have the "Engineer"
(phone jockey) with less knowledge than myself not be able to
comprehend my problem. In the end it was not resolved and I was still
charged.
CSL
Hi,
> Well now that you mention clntrust.exe, I have another forum running at
> the moment to resolve a problem where the gateway allows all users
> access (depending on ACL rules) without the need for Clntrust.exe at
> all. I did not even know that clntrust was needed until very recently,
> and we have been using the product in various forms for 3 years.
yeah, I am looking at that one, too.
I will reply there about this.
> I am reluctant to place a call with Novell technical support as last
> time they took 4 weeks to answer my call only to have the "Engineer"
> (phone jockey) with less knowledge than myself not be able to
> comprehend my problem. In the end it was not resolved and I was still
> charged.
you should have complained. If the call is not solved they can't close it, and if it is not closed
they can't charge for it.
You can always complain and ask for an "upgrade" of the call (where you get someone who has a certain
in depth knowledge of the product).
Anyway, I understand your frustration.
PeterH
how I have always done it as it is part of our defualt install.
Also how do I find out what version of the client trust we are running,
and what version should we be running?
Peter H