Sponsored Content
Operating Systems Linux Red Hat unable to mount windows share on linux 5.1 Post 302509997 by theboogymaster on Friday 1st of April 2011 09:34:22 AM
Old 04-01-2011
Take a look at this :

Using SAMBA/CIFS to access Windows Shares - PrincetonUnixFAQ

And you can specify the rw option for the mount command
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

using the mount command to connect to a windows share

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. AIX

Unable to mount NFS share during boot

Hello Everyone, I have a pseries machine running AIX 4.3.3 that has an invalid IP in /etc/hosts. During a boot the system hangs because it's trying to mount an NFS share to this invalid IP. I've tried to boot the system from a mksysb (not sure if the device was defined as rmt0) and AIX CD... (0 Replies)
Discussion started by: jlslhills
0 Replies

3. UNIX for Advanced & Expert Users

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... (2 Replies)
Discussion started by: rbdenham
2 Replies

4. Solaris

How to mount windows Share on solaris using SAMBA

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. UNIX for Advanced & Expert Users

can i mount nfs share on windows 2003 server

this is probably a bit dumb ...but i read somewhere that one of the nfs versions can be mounted on a windows 2003 server ..if yes ..does anyone know how this can be achieved (1 Reply)
Discussion started by: tarunicon
1 Replies

6. Red Hat

Mount Windows share on Redhat, WITHOUT Samba?

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

7. Solaris

how to mount Windows NFS share on 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

8. Solaris

mount windows share folder

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. AIX

AIX cifs: mount Windows Server 2008 share ?

Hello, I've been using AIX cifs to mount windows XP shares with no problems till now. Now it's Windows Server 2008 R2 - no go: mount -v cifs -n host1/user1/pass1 /share1 /mountpt1 There was an error connecting the share or the server. Make sure the lsdev command shows that device nsmb0 is in... (6 Replies)
Discussion started by: vilius
6 Replies

10. AIX

Unable to mount previously-working NFS share from NIM to LPAR

Right, now that I've finally worked out this website, I'll ask my question! I am having an absolute nightmare with NFS on AIX. I have used it many times, and I know what I'm doing, however I cannot fathom what is going on here. I have 2 LPARs, sitting on the same physical host. They are... (12 Replies)
Discussion started by: tmooredba
12 Replies
CIDR(3pm)						User Contributed Perl Documentation						 CIDR(3pm)

NAME
Net::CIDR - Manipulate IPv4/IPv6 netblocks in CIDR notation SYNOPSIS
use Net::CIDR; use Net::CIDR ':all'; print join(" ", Net::CIDR::range2cidr("192.68.0.0-192.68.255.255", "10.0.0.0-10.3.255.255")) . " "; # # Output from above: # # 192.68.0.0/16 # 10.0.0.0/14 print join(" ", Net::CIDR::range2cidr( "dead:beef::-dead:beef:ffff:ffff:ffff:ffff:ffff:ffff")) . " "; # # Output from above: # # dead:beef::/32 print join(" ", Net::CIDR::range2cidr("192.68.1.0-192.68.2.255")) . " "; # # Output from above: # # 192.68.1.0/24 # 192.68.2.0/24 print join(" ", Net::CIDR::cidr2range("192.68.0.0/16")) . " "; # # Output from above: # # 192.68.0.0-192.68.255.255 print join(" ", Net::CIDR::cidr2range("dead::beef::/46")) . " "; # # Output from above: # # dead:beef::-dead:beef:3:ffff:ffff:ffff:ffff:ffff @list=("192.68.0.0/24"); @list=Net::CIDR::cidradd("192.68.1.0-192.68.1.255", @list); print join(" ", @list) . " "; # # Output from above: # # 192.68.0.0/23 print join(" ", Net::CIDR::cidr2octets("192.68.0.0/22")) . " "; # # Output from above: # # 192.68.0 # 192.68.1 # 192.68.2 # 192.68.3 print join(" ", Net::CIDR::cidr2octets("dead::beef::/46")) . " "; # # Output from above: # # dead:beef:0000 # dead:beef:0001 # dead:beef:0002 # dead:beef:0003 @list=("192.68.0.0/24"); print Net::CIDR::cidrlookup("192.68.0.12", @list); # # Output from above: # # 1 @list = Net::CIDR::addr2cidr("192.68.0.31"); print join(" ", @list); # # Output from above: # # 192.68.0.31/32 # 192.68.0.30/31 # 192.68.0.28/30 # 192.68.0.24/29 # 192.68.0.16/28 # 192.68.0.0/27 # 192.68.0.0/26 # 192.68.0.0/25 # 192.68.0.0/24 # 192.68.0.0/23 # [and so on] print Net::CIDR::addrandmask2cidr("195.149.50.61", "255.255.255.248")." "; # # Output from above: # # 195.149.50.56/29 DESCRIPTION
The Net::CIDR package contains functions that manipulate lists of IP netblocks expressed in CIDR notation. The Net::CIDR functions handle both IPv4 and IPv6 addresses. @cidr_list=Net::CIDR::range2cidr(@range_list); Each element in the @range_list is a string "start-finish", where "start" is the first IP address and "finish" is the last IP address. range2cidr() converts each range into an equivalent CIDR netblock. It returns a list of netblocks except in the case where it is given only one parameter and is called in scalar context. For example: @a=Net::CIDR::range2cidr("192.68.0.0-192.68.255.255"); The result is a one-element array, with $a[0] being "192.68.0.0/16". range2cidr() processes each "start-finish" element in @range_list separately. But if invoked like so: $a=Net::CIDR::range2cidr("192.68.0.0-192.68.255.255"); The result is a scalar "192.68.0.0/16". Where each element cannot be expressed as a single CIDR netblock range2cidr() will generate as many CIDR netblocks as are necessary to cover the full range of IP addresses. Example: @a=Net::CIDR::range2cidr("192.68.1.0-192.68.2.255"); The result is a two element array: ("192.68.1.0/24","192.68.2.0/24"); @a=Net::CIDR::range2cidr( "d08c:43::-d08c:43:ffff:ffff:ffff:ffff:ffff:ffff"); The result is an one element array: ("d08c:43::/32") that reflects this IPv6 netblock in CIDR notation. range2cidr() does not merge adjacent or overlapping netblocks in @range_list. @range_list=Net::CIDR::cidr2range(@cidr_list); The cidr2range() functions converts a netblock list in CIDR notation to a list of "start-finish" IP address ranges: @a=Net::CIDR::cidr2range("10.0.0.0/14", "192.68.0.0/24"); The result is a two-element array: ("10.0.0.0-10.3.255.255", "192.68.0.0-192.68.0.255"). @a=Net::CIDR::cidr2range("d08c:43::/32"); The result is a one-element array: ("d08c:43::-d08c:43:ffff:ffff:ffff:ffff:ffff:ffff"). cidr2range() does not merge adjacent or overlapping netblocks in @cidr_list. @netblock_list = Net::CIDR::addr2cidr($address); The addr2cidr function takes an IP address and returns a list of all the CIDR netblocks it might belong to: @a=Net::CIDR::addr2cidr('192.68.0.31'); The result is a thirtythree-element array: ('192.68.0.31/32', '192.68.0.30/31', '192.68.0.28/30', '192.68.0.24/29', [and so on]) consisting of all the possible subnets containing this address from 0.0.0.0/0 to address/32. Any addresses supplied to addr2cidr after the first will be ignored. It works similarly for IPv6 addresses, returning a list of one hundred and twenty nine elements. $cidr=Net::CIDR::addrandmask2cidr($address, $netmask); The addrandmask2cidr function takes an IP address and a netmask, and returns the CIDR range whose size fits the netmask and which contains the address. It is an error to supply one parameter in IPv4-ish format and the other in IPv6-ish format, and it is an error to supply a netmask which does not consist solely of 1 bits followed by 0 bits. For example, '255.255.248.192' is an invalid netmask, as is '255.255.255.32' because both contain 0 bits in between 1 bits. Technically speaking both of those *are* valid netmasks, but a) you'd have to be insane to use them, and b) there's no corresponding CIDR range. @octet_list=Net::CIDR::cidr2octets(@cidr_list); cidr2octets() takes @cidr_list and returns a list of leading octets representing those netblocks. Example: @octet_list=Net::CIDR::cidr2octets("10.0.0.0/14", "192.68.0.0/24"); The result is the following five-element array: ("10.0", "10.1", "10.2", "10.3", "192.68.0"). For IPv6 addresses, the hexadecimal words in the resulting list are zero-padded: @octet_list=Net::CIDR::cidr2octets("::dead:beef:0:0/110"); The result is a four-element array: ("0000:0000:0000:0000:dead:beef:0000", "0000:0000:0000:0000:dead:beef:0001", "0000:0000:0000:0000:dead:beef:0002", "0000:0000:0000:0000:dead:beef:0003"). Prefixes of IPv6 CIDR blocks should be even multiples of 16 bits, otherwise they can potentially expand out to a 32,768-element array, each! @cidr_list=Net::CIDR::cidradd($block, @cidr_list); The cidradd() functions allows a CIDR list to be built one CIDR netblock at a time, merging adjacent and overlapping ranges. $block is a single netblock, expressed as either "start-finish", or "address/prefix". Example: @cidr_list=Net::CIDR::range2cidr("192.68.0.0-192.68.0.255"); @cidr_list=Net::CIDR::cidradd("10.0.0.0/8", @cidr_list); @cidr_list=Net::CIDR::cidradd("192.68.1.0-192.68.1.255", @cidr_list); The result is a two-element array: ("10.0.0.0/8", "192.68.0.0/23"). IPv6 addresses are handled in an analogous fashion. $found=Net::CIDR::cidrlookup($ip, @cidr_list); Search for $ip in @cidr_list. $ip can be a single IP address, or a netblock in CIDR or start-finish notation. lookup() returns 1 if $ip overlaps any netblock in @cidr_list, 0 if not. $ip=Net::CIDR::cidrvalidate($ip); Validate whether $ip is a valid IPv4 or IPv6 address, or a CIDR. Returns its argument or undef. Spaces are removed, and IPv6 hexadecimal address are converted to lowercase. If $ip contains a "/", it must be a valid CIDR, otherwise it must be a valid IPv4 or an IPv6 address. A technically invalid CIDR, such as "192.168.0.1/24" fails validation, returning undef. BUGS
Garbage in, garbage out. Always use cidrvalidate() before doing anything with untrusted input. Otherwise, "slightly" invalid input will work (extraneous whitespace is generally OK), but the functions will croak if you're totally off the wall. AUTHOR
Sam Varshavchik <sam@email-scan.com> With some contributions from David Cantrell <david@cantrell.org.uk> perl v5.14.2 2012-05-01 CIDR(3pm)
All times are GMT -4. The time now is 11:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy