Subject | RE: [ib-support] Re: Accessing Interbase on a LAN |
---|---|
Author | Andrew Barton |
Post date | 2001-02-16T18:33:16Z |
In networking properties have you set up static IP's and subnet masks? If
you are running an Win9x peer to peer network with only two devices on the
network, there is no DHCP server to dynamically allocate addresses. Putting
IP's in the hosts file on it's own is not enough.
How about the cabling, is it OK? Do you have netbeui running as well?
HTH
Andrew Barton
you are running an Win9x peer to peer network with only two devices on the
network, there is no DHCP server to dynamically allocate addresses. Putting
IP's in the hosts file on it's own is not enough.
How about the cabling, is it OK? Do you have netbeui running as well?
HTH
Andrew Barton
> -----Original Message-----
> From: mss@... [mailto:mss@...]
> Sent: Friday, February 16, 2001 8:43 AM
> To: ib-support@yahoogroups.com
> Subject: [ib-support] Re: Accessing Interbase on a LAN
>
>
> Perhaps the whole problem boils down to my not being able to ping the
> server.
>
> On the server PC, I've set an IP address of 192.168.0.1 using Control
> Panel - Networking.
>
> From the work station, when I try to ping this IP address, I get the
> message "Destination Host Unreachable". Yet, clearly I am
> networked. I can access various programs and files accross the
> network, for example. Perhaps the problem has something to do with
> the TCP/IP protocol.
>
> I do have the entry set correctly in the Hosts file. The entry looks
> like this:
>
> 192.168.0.1 GatewayDesktop
>
> (I've defined the Server Name as GatewayDesktop under Control Panel -
> Network - Identification.)
>
> Any ideas?
>
> Thanks.
>
> - Dale F.
>
>
>
> --- In ib-support@y
>
>
> --- In ib-support@y..., lester@l... wrote:
> > Win95 has rather poor network support, so it may be necessary to use
> > Netbeui protocol rather than TCP/IP, but TCP/IP is prefered.
> >
> > That is "\\Gateway desktop\c\MyPath\MyData.gdb", '\c\' should be the
> > shared name for the c drive on that machine.
> >
> > I don't think you can use spaces in a machine name. This has to be a
> > 'single word', so it is normal to use the '_' (underscore) if a
> space
> > would help readability. If you have a space in the HOSTS file, it
> will
> > not find the address!
> >
> > If TCP/IP is correctly set up on the machine, and I forget how to
> get to
> > it's setting in W95 - we NEVER deployed it to customer site as it
> was
> > too unstable!
> > Control Panel - Network - is used on W98.
> > There should be an entry for 'Gateway' which allows you to set the
> > machine address of your main server. Also we normally un-install the
> > dialer and re-install it so that it comes after the network
> connection
> > in 'bind' order, but again - not sure if this will work on W95
> >
> > W98SE has a lot of these little problems fixed so all our sites have
> > been upgraded to that ( and if Microsoft want more money off us
> because
> > we have not got enough SE licenses they will have to prove previous
> > issues were 'fit for purpose' ! ).
> >
> > HOSTS file should have
> >
> > SERVER 192.168.0.1
> > CLIENT 192.168.0.2
> >
> > on both machines ( you can then just copy one file to the other
> machine
> > if need be )
> >
> > From a DOS prompt you should be able to
> > PING SERVER
> > and
> > PING CLIENT
> >
> > If either of these do not work, then you still have a network
> problem. (
> > The dialer can be killed if it pops up, the ping should still
> work ).
> >
> > Once you have this working - then you can try "Diagnose
> Connection..."
> > using the TCP/IP settings.
> >
> > --
> > Lester Caine
> > -----------------------------
> > L.S.Caine Electronic Services
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>