Michael
As far as I am aware, I didn't do anything. Do these entries look odd
then?
Regards
Ashley
On Mon, 2003-02-03 at 13:01, Michael Schwendt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04 Feb 2003 17:39:12 -0500, Ashley Kitson wrote:
>
> > http://127.0.0.1:901 works!!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04 Feb 2003 17:39:12 -0500, Ashley Kitson wrote:
> http://127.0.0.1:901 works!! brilliant
>
> However, in case this is helping anyone else my /etc/hosts file contains
>
> 192.168.1.102 Prospect3
> 192.168.1.100 Prospect2
> 192.168.
Nick
Thanks for the help. The eth0 address is what I know as my local
machine address. As you can see from a reply to Michael, the loopback
address works as well (http://127.0.0.1:901).
Regards
Ashley
On Mon, 2003-02-03 at 12:25, Nick Lindsell wrote:
> At 17:06 04/02/2003 -0500, you wrote:
>
Michael
http://127.0.0.1:901 works!! brilliant
However, in case this is helping anyone else my /etc/hosts file contains
192.168.1.102 Prospect3
192.168.1.100 Prospect2
192.168.1.101 Prospect1 localhost
192.168.1.101 Prospect1.Prospect
Prospect 2 and 3 were entered b
At 17:06 04/02/2003 -0500, you wrote:
Nick
I don't recall seeing that IP address anywhere. Where might I find it?
From a command line:-
"ifconfig" - you're probably looking for the eth0 device if you have only
one network card.
hih
nick@nexnix
Regards
Ashley
> Use the IP address of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04 Feb 2003 16:28:38 -0500, Ashley Kitson wrote:
> However .. Now instead of Mozilla telling me I cannot connect when I
> type in the http://localhost:901/ url I get an alert message stating
> that 'The operation timed out when attempting to contac
Nick
I don't recall seeing that IP address anywhere. Where might I find it?
Regards
Ashley
> Use the IP address of the samba server instead of localhost.
> This will also allow you access from other machines so you don't
> have to run X on the server.
>
> hih
> nick@nexnix
>
--
redhat-l
At 16:28 04/02/2003 -0500, you wrote:
However .. Now instead of Mozilla telling me I cannot connect when I
type in the http://localhost:901/ url I get an alert message stating
that 'The operation timed out when attempting to contact
www.localhost.com' This is progress of sorts I guess :-)
Any id
Bret
Thanks for that. I had to force rpm to de-install using --notriggers
--noscripts but it did clear samba out. I've now re-installed and 'rpm
-qa|grep samba' now gives
samba-2.2.5-10
samba-common-2.2.5-10
samba-client-2.2.5-10
samba-swat-2.2.5-10
I then did
chkconfig smb on
chkconfig sw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04 Feb 2003 13:00:40 -0500, Ashley Kitson wrote:
> samba-common-2.2.5-10
> samba-2.2.7a-1
> samba-client-2.2.5-10
>
> so it's mixed up! What now?
As "root" user:
rpm --erase samba --nodeps
up2date --nox samba-swat
The 2.2.7a-1 package is no
On Tue, 2003-02-04 at 12:00, Ashley Kitson wrote:
> Bret
>
> Thanks. here is output
>
> samba-common-2.2.5-10
> samba-2.2.7a-1
> samba-client-2.2.5-10
>
> so it's mixed up! What now?
>
OK
keep in mind I am not an up2date user and there may be a better way to
do this using the tool.
This sh
Bret
Thanks. here is output
samba-common-2.2.5-10
samba-2.2.7a-1
samba-client-2.2.5-10
so it's mixed up! What now?
Kind Regards
Ashley
On Sun, 2003-02-02 at 16:28, Bret Hughes wrote:
>
> New point of view with no 8.0 experience.
>
> First, what does rpm think you have
>
> what does
>
> r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03 Feb 2003 20:57:52 -0500, Ashley Kitson wrote:
> > This is not true for Red Hat's samba-swat packages. There the server
> > line points to /usr/sbin/swat. Whatever you did, you damaged the
> > xinetd config files in several places.
>
> Whatever
On Mon, 2003-02-03 at 19:57, Ashley Kitson wrote:
> Michael
>
>
> You miss the point. here is a timeline:
>
> 1/ RH6.2 Loaded sometime back
> 2/ Machine nuked
> 3/ RH 8.0 loaded including Samba
> 4/ RH autoupdate updates Samba to 2.2.7
> 5/ I get around to using it, configure Samba to run manual
Michael
> This is not true for Red Hat's samba-swat packages. There the server
> line points to /usr/sbin/swat. Whatever you did, you damaged the
> xinetd config files in several places.
Whatever I did, was done under strict direction from the install
directions from the RH8 install guide and fol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 31 Jan 2003 17:20:19 -, Ashley Kitson wrote:
> Thanks for persevering. I ran the tail on messages as suggested. It
> turned out that the server= line in the /etc/xinetd.d/swat file is
> pointing to something that doesn't exist (it reads
Michael
Thanks for persevering. I ran the tail on messages as suggested. It turned
out that the server= line in the /etc/xinetd.d/swat file is pointing to
something that doesn't exist (it reads server=/etc/xinetd/swat i.e. itself).
The log message shows that the server doesn't exist. That got m
17 matches
Mail list logo
