> >> If the client is running Win9x, 3.1, NT 3.51 or NT4 then everything
> is OK, but if the client is running Win2K it bungs up? If I assume
> this is correct, then it's an incompatability some where.
> >> Can I make the assumption, that the Win2K clients see the Netware
> server, and can do anything except access the BDE stuff. Then it's
> either that BDE or the IB client is the problem.
> It isn't the IB Client. ISQL and Database Manager work fine.
If ISQL and Database Manager work, then it comes down to one thing, the
BDE or most likely a conflict between Win2K and the BDE that you are
using. It may have nothing to do with IPX and Netware, but lots to
do with the BDE and Win2K. You need to check Borlands web site, and
see if there is a newer version of the BDE then the one you are
using. If your using a BDE that shipped before the IPX drivers for
Win2K were finalised then that could be causing the problem.
> >> 1) Put a Linux box running IB6 or Firebird into the server rack,
> >> with
> a DHCP server running, no fuss, no muss TCP/IP, client machines get
> their IP address from the server, assigned from the 192.168.x.x
> blocks, these addresses can not be used to access the internet, and
> the internet can't find them either. If the client at some future
> date wants Internet Access, a firewall and NAT server can be
> installed. The client uses Netware and IPX/SPX for everything else,
> such a dual protocol network runs fine for me, here. You avoid the
> IPX protocol for IB completely, and many of the other problems as
> Good idea, I'll pass that along to support as a suggestion. I didn't
> think about the 192.168.x.x not being accessible from outside.
There are a couple of other blocks, I think that 10.x.x.x is
available the same way, look to see if you can find a DHCP server for
Netware, if you can't go through the junk room, dig out a working 486
put Linux on it, and use that as a DHCP server, if you run named
(DNS) on it as well, you can link the two together, so that when a
machine leases an IP address it gets linked to it's machine name.
All the client needs to know is where the DHCP and DNS server are,
and it's much easier then trying to figure out what IP addresses are
in use, and which ones are not. If Netware (the only Netware book I
have doesn't tell me) has IP set up properly, then it can also act as
a DHCP client, so that the server itself leases it's IP address from
the pool (if it can't you simply assign the Linux and Netware servers
a fixed IP address and assign them in DNS). The old 486 running
Linux, is actually better in that in the future, if the client needs
to have workstations access the internet, you simply add a NAT server
(software that does IP Masquerading) and firewall. They only need
"real" IP addresses for the Linux box and web server. Adding new
PC's is a piece of cake, simply tell them where the DNS server and
DHCP server are.
> Those were some good suggestions. Thanks Paul.