07-09-2008
How to Mount a Unix share drive on Windows
We are trying to mount a Unix share drive on a Windows 2003 server to avoid transfering files accross the network using sftp. I can see shared drives on the Solaris server using the "share" command. How can I mount the drives on my Windows server so that I can read them directly. Do I need anything installed in Windows to do this? Unix services for Windows? I would like to see the details steps involved if possible. Commands ..etc. Please help us out.
Rich
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Until recently I have been using the following command successfully to connect to a windows share:
mount -t smbfs -o username=my_username,password=my_password /home/temp //oldserverx1/openexchange
But from today, I've been getting the following error:
INFO: Debug class all level = 1 (pid... (1 Reply)
Discussion started by: cw1972
1 Replies
2. UNIX for Dummies Questions & Answers
Hi, I would like to be able to mount windows xp to a unix system, so that I can pull data from windows machine for backup and store it on the unix server. Does anyone know how I can go about mounting the windows drive in unix.
Thanks,
Eric (4 Replies)
Discussion started by: ejbrever
4 Replies
3. AIX
Dear all,
How can mount a drive from AIX 4.3 to Windows 2003 Server share folder ?
Thank a lot. (1 Reply)
Discussion started by: sinopec
1 Replies
4. Solaris
Hi All
I am new for Solaris and, I have configured SAMBA on my SUN10 Network machine and it's working fine.
can anyone tell me how to mount windows share on my SUN10 machine.
Thanks in advance
daya (2 Replies)
Discussion started by: daya.pandit
2 Replies
5. Red Hat
Hi,
Please let me know whether I can mount a windows share on Redhat, which does not have Samba installed. The constraint is that I cannot install Samba .
Looking forward for a possible solution. (1 Reply)
Discussion started by: jksena
1 Replies
6. Solaris
Hi, How can i mount an NFS share on a solaris machine a filesystem ?
I have enabled nfs on a windows server and the shares has given read/write access to it to all the users. I would like to mount it on around 10 different solaris boxes with different versions of solaris.
Thanks in advance. (2 Replies)
Discussion started by: uxadmin007
2 Replies
7. Solaris
I'm trying to setup Samba in a solaris zone... Is there a way to setup Samba so that every Windows machine that tries to connect to the share always gets it mounted under the same drive letter (e.g. H:)???
My Samba share (in smb.conf)
/home/pickup
I want that all Window users get it mounted... (3 Replies)
Discussion started by: verdepollo
3 Replies
8. Solaris
all,,i need help,,i try to mount a windows 2000 share folder to my system,,i already userd smb mount,mount -F and bunch of stuff and none is working,,can anyone give me a script to this??
PS : when i use mount -F i got this message :
nfs mount: insufficient privileges ,,,
is it must be root ? (6 Replies)
Discussion started by: Cellscript
6 Replies
9. Red Hat
Hi,
I am using redhat linux 5.1 - 64bit,
using command
mount -t cifs //192.192.192.192/SW/Ex /192.192.192.192 -o username=test
I am getting below error.
mount: block device //192.192.192.192/SW/Ex is write-protected, mounting read-only
mount: cannot mount block device... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
10. AIX
Hi,
How can we share a AIX drive on to Windows 2012 server. or vise versa.
Note: Not using NFS/CIFS/samba. (*we are not able to use samba/NFS/CIFS for some reason)
Requirement: How to have real time file sharing over the network between Windows and UNIX
Do you guys have any ... (4 Replies)
Discussion started by: System Admin 77
4 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)