Sponsored Content
Operating Systems Solaris new sparc netra 500mhz problem Post 302255503 by pupp on Thursday 6th of November 2008 02:28:00 PM
Old 11-06-2008
i take it you have a ms windows environment so i would look into 1 of 2 services... ftp or samba.
 

10 More Discussions You Might Find Interesting

1. Solaris

Netra T1 105 problem

Hey All Thanks in Advance. Iam facing a problem with Netra T1 105 Ram issuse.I have 1 gb ram in the server but when it boots up in ok prompt or in banner it shows 768 mb Ram , if i put 512 mb Ram it show 368 mb Ram but this all ram if i connect in anthore netra server its shows 1 gb and... (1 Reply)
Discussion started by: solaris8in
1 Replies

2. Solaris

Netra V440 & Netra 1290 keyswitch

Hello, I wrote a script which monitor the keyswitch state repeatedly each 10 minutes. I'm extracting the keyswitch status by using prtdiag. The script works fine for Netra v440 , but I found that prtdiag under Netra 1290 don't give keyswitch status. unlike Netra 440 server , I found that... (2 Replies)
Discussion started by: Alalush
2 Replies

3. Solaris

Problem using default account with ILOM on Sun SPARC Enterprise T5140

Hi, I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies

4. Debian

Problem installing Debian5 on an ultra sparc machine

Comments/Problems: Machine boots from CDROM, starts SILO Version 1.4.13, display welcome message (welcome to Debian GNU/Linux lenny! built on 20081218-10:06 ). boot: Allocated 8 Megs of memory at 0x40000000 for kernel Loaded kernel version 2.6.26 Loading initial ramdisk... (3 Replies)
Discussion started by: mtk
3 Replies

5. Solaris

Netra Remote Dial-in Problem

Looking for ideas on why I can't dial into our new Avaya CMS server (Sun Netra 210 - Sol 9) - remotely thru our ASA - site admin software. Running R3-V13 Avaya CMS software - just did a fresh install of the CMS software - install went perfect. The Sun supplied DB9 connector is installed... (1 Reply)
Discussion started by: drewmich
1 Replies

6. Solaris

Netra T2000 /var/adm/messages problem

Hi, I have a netra t2000 running solaris 10. It is fully patched with the latest patch cluster and also patch 118833-36 and 126897-02. The SC sys_event level is set to 3. I am running a test to show hardware log status, e.g simulating a power supply failure.Hence I unplug one of te... (3 Replies)
Discussion started by: ulemsee
3 Replies

7. Ubuntu

Ubuntu 8 SPARC edition problem jumbled text at install

hello guys i bought a SPARC neutra system a couple of months ago and after failing to install solaris onto it (and leaving it as a door stop for a couple of months) decided to stick ubuntu onto it for starters i dont own a sun keyboard i have a cheap pcline usb keyboard (it works... (3 Replies)
Discussion started by: garethmob
3 Replies

8. Solaris

Boot problem with SUN Sparc

Newbie question. I've been running OpenSolaris on an Intel box for some time with great success. I have just bought an old Sun Blade workstation with a corrupted version of Solaris 5 something on it. The plan was to install OpenSolaris on it. However beyond my skills, I see, as no Live CD (or... (10 Replies)
Discussion started by: lewtargett
10 Replies

9. Solaris

SUN SPARC rebooting problem, after Solaris 10 installation

Hi All, I had install the solaris 10 into the SUNFIRE V890 server, after installed, it keep rebooting. I wish to enter the OK mode again, and install back the Solaris 10. i had try the "break" button and "stop+A" button, but all fail. kindly advice... (4 Replies)
Discussion started by: SmartAntz
4 Replies

10. Hardware

POST displays error sparc netra 240

Hi guys, when I power on my sun netra 240 server, it displays these error messages: 1. Notice: cpu 0 has 2048/2048 MB of memory disabled. 2. Error : The following devices are disabled dimm1. Please can anyone be kind enough to explain this for me? Thanks (2 Replies)
Discussion started by: cjashu
2 Replies
SWAT(8) 																   SWAT(8)

NAME
swat - Samba Web Administration Tool SYNOPSIS
swat [ -s <smb config file> ] [ -a ] DESCRIPTION
This tool is part of the Samba suite. swat allows a Samba administrator to configure the complex smb.conf(5) file via a Web browser. In addition, a swat configuration page has help links to all the configurable options in the smb.conf file allowing an administrator to easily look up the effects of any change. swat is run from inetd OPTIONS
-s smb configuration file The default configuration file path is determined at compile time. The file specified contains the configuration details required by the smbd server. This is the file that swat will modify. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See smb.conf for more infor- mation. -a This option disables authentication and puts swat in demo mode. In that mode anyone will be able to modify the smb.conf file. Do NOT enable this option on a production server. INSTALLATION
After you compile SWAT you need to run make install to install the swat binary and the various help files and images. A default install would put these in: o /usr/local/samba/bin/swat o /usr/local/samba/swat/images/* o /usr/local/samba/swat/help/* INETD INSTALLATION You need to edit your /etc/inetd.conf and /etc/services to enable SWAT to be launched via inetd. In /etc/services you need to add a line like this: swat 901/tcp Note for NIS/YP users - you may need to rebuild the NIS service maps rather than alter your local /etc/services file. the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your inetd daemon). In /etc/inetd.conf you should add a line like this: swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat One you have edited /etc/services and /etc/inetd.conf you need to send a HUP signal to inetd. To do this use kill -1 PID where PID is the process ID of the inetd daemon. XINETD INSTALLATION Newer Linux systems ship with a more secure implementation of the inetd meta-daemon. The xinetd daemon can read configuration inf9ormation from a single file (i.e. /etc/xinetd.conf) or from a collection of service control files in the xinetd.d/ directory. These directions assume the latter configuration. The following file should be created as /etc/xientd.d/swat. It is then be neccessary cause the meta-daemon to reload its configuration files. Refer to the xinetd man page for details on how to accomplish this. ## /etc/xinetd.d/swat service swat { port = 901 socket_type = stream wait = no only_from = localhost user = root server = /usr/local/samba/bin/swat log_on_failure += USERID disable = No } LAUNCHING To launch SWAT just run your favorite web browser and point it at "http://localhost:901/". Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire. TROUBLESHOOTING
One of the common causes of difficulty when installing Samba and SWAT is the existsnece of some type of firewall or port filtering software on the Samba server. Make sure that the appropriate ports outlined in this man page are available on the server and are not currently being blocked by some type of security software such as iptables or "port sentry". For more troubleshooting information, refer to the additional documentation included in the Samba distribution. FILES
/etc/inetd.conf This file must contain suitable startup information for the meta-daemon. /etc/xinetd.d/swat This file must contain suitable startup information for the xinetd meta-daemon. /etc/services This file must contain a mapping of service name (e.g., swat) to service port (e.g., 901) and protocol type (e.g., tcp). /usr/local/samba/lib/smb.conf This is the default location of the smb.conf(5) server configuration file that swat edits. Other common places that systems install this file are /usr/samba/lib/smb.conf and /etc/smb.conf . This file describes all the services the server is to make available to clients. WARNINGS
swat will rewrite your smb.conf file. It will rearrange the entries and delete all comments, include= and copy=" options. If you have a carefully crafted smb.conf then back it up or don't use swat! VERSION
This man page is correct for version 2.2 of the Samba suite. SEE ALSO
inetd(5), smbd(8) smb.conf(5) xinetd(8) AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter 19 November 2002 SWAT(8)
All times are GMT -4. The time now is 09:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy