Accessing shares on CentOS server

Since the 10.6.5 update, we are seeing some issues writing and deleting files to share(s) on our CentOS server. We can log on, see the share, browse and read and write. If we remove a file, in this case an index.html file, and try to place a file by the same name back to the share. It says a newer file of that name already exists. We choose write over it and it says something about a file named "".
If we delete and write the file using an FTP client, like Transmit, we have no issues.
We can only correlate this issue with the 10.6.5 update as we have been reading and writing to these shares on the CentOS servers with no issues in the past.

Sravanti - I see that about 1.5 years ago you had a problem when trying to use the JavaMail API to retrieve messages from an Exchange mailbox: "A2 NO There is no replica for that mailbox on this server". I am getting that same problem - did you resolve that issue? What was the problem?
Any help would be greatly appreciated.
-clint

Similar Messages

Trying to access share on Microsoft Server 2k HELP

Have been pulling my hair out for 2 days on this.
Any help would be appreciated.
I support a medium sized network here. About 60 stations. All XP or Win 7 machines in the office.
Our new design guy has a Mac book pro running 10.8.1. Brand new out of box.
I am trying to access a share on our server. The server I am trying to access the share on is running Microsoft Server 2000.
I have never had an issue mapping this share as a drive on a windows machine.
The Mac does see the server in its directory, but I can not access it.
I have tried the
smb://servername/sharename and smb://IP of server/sharename
Both of these methods give me a screen to enter credentials but then it shakes them off.
If I try to enter the share via the directory I get a message saying the connection failed.
Any ideas?

I have the same problem. There is a lengthy discussion on it over at https://discussions.apple.com/thread/4145388?tstart=0 But still no fix yet. I have multiple Macs with this problem. I have been playing sneaker-net at work because of it. Upgrading my mission critical server past and above Win2000 server is not possible at this point. Not really happy to learn this after the ML upgrade. I wish I could go back to Lion then I would not have this problem.

I can't access folder share in WIndows Server 2012 R2 from windows 8.1

i have a strange case:
I have a Windows Server 2012 R2 machine with a shared folder. Accessing this folder using a Win7, Win8,
Win 2008 R2 machine using \\servername works fine but form windows 8.1 or windows
2012 r2 i can't so any one can help me.

Hi,
Would you please let me know the complete error message that you can find, when can’t access to the share folder
that host in the Windows Server 2012 R2?
If you logon the Windows 8.1 (or server 2012 r2) with administrator account, will encounter the same issue?
Meanwhile, please access the share folder via \\server’s IP address\share folder. Then please check if this issue still persists.
In addition, there is a similar thread. Please refer to and check if can help you.
Can't
access UNC share on Windows Server 2012 R2
Hope this helps.
Best regards,
Justin Gu

User Can Browse Network Server But Not Access Share

I have a client computer that can access shares on a network, however on server the user cannot access a specific shared folder.
Client is Windows 7 joined to domain
Client can access shares on other servers and other shared folders on the problem server
I have checked effective permissions for the user and they have modify permission on the folder/subfolders
Share is Everyone - FC
Have explicitly added user to share with FC permissions as well.
Server is 2012.
The error I am getting is The Specified Network Name is No Longer Available
Other users do not have this issue.
User can access share from another client.

Hi,
Thank you for the update.
Best regards
Michael Shao
TechNet Community Support

I need helping!!! configuring RDP access to my local server from a remote location on my Cisco ASA 5505 Firewall.

I need helping configuring RDP access to my local server from a remote location on my Cisco ASA 5505 Firewall.
I have attempted to configure rdp access but it does not seem to be working for me Could I please ask someone to help me modify my current configuration to allow this? Please do step by step as I could use all the help I could get.
I need to allow the following IP addresses to have RDP access to my server:
66.237.238.193-66.237.238.222
69.195.249.177-69.195.249.190
69.65.80.240-69.65.80.249
My external WAN server info is - 99.89.69.333
The internal IP address of my server is - 192.168.6.2
The other server shows up as 99.89.69.334 but is working fine.
I already added one server for Static route and RDP but when I try to put in same commands it doesnt allow me to for this new one. Please take a look at my configuration file and give me the commands i need in order to put this through. Also please tell me if there are any bad/conflicting entries.
THE FOLLOWING IS MY CONFIGURATION FILE
Also I have modified IP information so that its not the ACTUAL ip info for my server/network etc... lol for security reasons of course
Also the bolded lines are the modifications I made but that arent working.
ASA Version 7.2(4)
hostname ciscoasa
domain-name default.domain.invalid
enable password DowJbZ7jrm5Nkm5B encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
interface Vlan1
nameif inside
security-level 100
ip address 192.168.6.254 255.255.255.0
interface Vlan2
nameif outside
security-level 0
ip address 99.89.69.233 255.255.255.248
interface Ethernet0/0
switchport access vlan 2
interface Ethernet0/1
interface Ethernet0/2
interface Ethernet0/3
interface Ethernet0/4
interface Ethernet0/5
interface Ethernet0/6
interface Ethernet0/7
ftp mode passive
dns server-group DefaultDNS
domain-name default.domain.invalid
object-group network EMRMC
network-object 10.1.2.0 255.255.255.0
network-object 192.168.10.0 255.255.255.0
network-object 192.168.11.0 255.255.255.0
network-object 172.16.0.0 255.255.0.0
network-object 192.168.9.0 255.255.255.0
object-group service RDP tcp
description RDP
port-object eq 3389
object-group service GMED tcp
description GMED
port-object eq 3390
object-group service MarsAccess tcp
description MarsAccess
port-object range pcanywhere-data 5632
object-group service MarsFTP tcp
description MarsFTP
port-object range ftp-data ftp
object-group service MarsSupportAppls tcp
description MarsSupportAppls
port-object eq 1972
object-group service MarsUpdatePort tcp
description MarsUpdatePort
port-object eq 7835
object-group service NM1503 tcp
description NM1503
port-object eq 1503
object-group service NM1720 tcp
description NM1720
port-object eq h323
object-group service NM1731 tcp
description NM1731
port-object eq 1731
object-group service NM389 tcp
description NM389
port-object eq ldap
object-group service NM522 tcp
description NM522
port-object eq 522
object-group service SSL tcp
description SSL
port-object eq https
object-group service rdp tcp
port-object eq 3389
access-list outside_1_cryptomap extended permit ip 192.168.6.0 255.255.255.0 object-group EMRMC
access-list inside_nat0_outbound extended permit ip 192.168.6.0 255.255.255.0 192.168.0.0 255.255.0.0
access-list inside_nat0_outbound extended permit ip 192.168.6.0 255.255.255.0 object-group EMRMC
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 host 99.89.69.334 eq pcanywhere-data
access-list outside_access_in extended permit udp 69.16.158.128 255.255.255.128 host 99.89.69.334 eq pcanywhere-status
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 host 99.89.69.334 object-group RDP
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 192.168.6.0 255.255.255.0 eq ftp
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 192.168.6.0 255.255.255.0 eq ldap
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 192.168.6.0 255.255.255.0 eq h323
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 192.168.6.0 255.255.255.0 eq telnet
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 192.168.6.0 255.255.255.0 eq www
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 host 99.89.69.334 object-group SSL
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 192.168.6.0 255.255.255.0 object-group NM522
access-list outside_access_in extended permit tcp 69.16.158.128 255.255.255.128 192.168.6.0 255.255.255.0 object-group NM1731
access-list outside_access_in extended permit tcp 173.197.144.48 255.255.255.248 host 99.89.69.334 object-group RDP
access-list outside_access_in extended permit tcp any interface outside eq 3389
access-list outside_access_in extended permit tcp host 66.237.238.194 host 99.89.69.333
access-list outside_access_in extended permit tcp host 66.237.238.194 host 99.89.69.333 object-group rdp
access-list outside_access_in extended permit tcp any host 99.89.69.333 object-group rdp
access-list out_in extended permit tcp any host 192.168.6.2 eq 3389
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-524.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 0.0.0.0 0.0.0.0
static (inside,outside) tcp 99.89.69.334 3389 192.168.6.1 3389 netmask 255.255.255.255
static (inside,outside) tcp interface 3389 192.168.6.2 3389 netmask 255.255.255.255
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 99.89.69.338 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
http server enable
http 192.168.6.0 255.255.255.0 inside
http 0.0.0.0 0.0.0.0 outside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto map outside_map 1 match address outside_1_cryptomap
crypto map outside_map 1 set peer 68.156.148.5
crypto map outside_map 1 set transform-set ESP-3DES-MD5
crypto map outside_map interface outside
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash md5
group 1
lifetime 86400
crypto isakmp policy 30
authentication pre-share
encryption 3des
hash md5
group 2
lifetime 86400
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
tunnel-group 68.156.148.5 type ipsec-l2l
tunnel-group 68.156.148.5 ipsec-attributes
pre-shared-key *
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
service-policy global_policy global
prompt hostname context
Cryptochecksum:f47dfb2cf91833f0366ff572eafefb1d
: end
ciscoasa(config-network)#

Unclear what did not work. In your original post you include said some commands were added but don't work:
static (inside,outside) tcp interface 3389 192.168.6.2 3389 netmask 255.255.255.255
and later you state you add another command that gets an error:
static (inside,outside) tcp 99.89.69.333 3389 192.168.6.2 3389 netmask 255.255.255.255
You also stated that 99.89.69.333 (actually 99.89.69.233, guessing from the rest of your config and other posts) is your WAN IP address.
The first static statement matches Cisco's documentation, which states that a static statement must use the 'interface' directive when you are trying to do static PAT utilizing the IP address of the interface. Since 99.89.69.333 is the assigned IP address of your WAN interface, that may explain why the second statement fails.
Any reason why you are using static PAT (including the port number 3389) instead of just skipping that directive? Static PAT usually makes sense when you need to change the TCP port number. In your example, you are not changing the TCP port 3389.

Access share on NSS4000 with error: A device attached to the system is not functioning

Hello,
We use Acronis True Image Server to backup 4 Windows 2008 Standard Server system
with 2 different domains, each containing a DC and a RDP-Server.
After Server reboot, backup will run only once a day.
The next day backup aborts, and while trying to access
the network share like \\ip-address\share, as configured in Acronis
I get the error message: A device attached to the system is not functioning.
On the other hand, I can ping the NSS4000 and access share by using the
network (netbios) name instead of the ip.
This will work only for one day, also.
Now, if I try to access the share on the NSS4000 again by ip,
I get the error code 0x80070043 The networkname can not be found.
Ping on ip and netbiosname works.
Share access from one server to an other is not affected and full funtional at all times.
On the first sight I thought, that there it might be with the authentication protocol NTLMV2.
So I configured the GP to send only NTLM Authentication only, without fixing the problem.
Fyi:
I use a NSS4000, Firmware version 1.16-3
The NSS4000 is not a member in neither domains.
I created a dummy user account on each domain, an created a local user on the NSS4000 related
to the dummy user account on each domain.
A good answer helping me to fix with this issue, would be great.

I am constantly seeing this error at multiple sites on Windows Server 2012 and 2012 R2 Standard and DataCenter.
I have counted over 50 different server I manage with services such as domain controller, hyper-v, file servers, exchange 2013, SQL 2008/2012, and print servers.
I have seen it happen on machine that have been in production for over 2 years and to machines that were just created last week.
It is happening on metal, hyper-v and esx vmware servers.
It is happening when the machine have updates waiting or no updates, or after updates have been applied and awaiting a restart.
It is happening on Dell PowerEdge server, HP Proliant servers and IBM servers.
It is happening on servers with Intel and AMD chip-sets.
It is happening on machines that are a part of a domain or in a workgroup.
It is happening on machines with AV of Bitdefendor, Trend Micro, Vipre, Microsoft Endpoint, and Symantec Endpoint.
Only a restart will fix it.
I have ran process monitor on several of the problem machines and I cannot find anything.
Since I have only started seeing this about 6 month ago it must be a Windows update causing it.
Moses Hull of Alexant Systems

Error while adding file share for File Server role

I'm getting this error when trying to add a file share on a Server 2012 R2 failover cluster:
"Unable to retrieve all data needed to run the wizard. Error details: Cannot retrieve information from server. Error occurred during enumeration of SMB shares: WinRM cannot complete the operation. Verify that the specified computer name is valid, that
the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote comptuers within the same
local subnet."
Despite the message, I can still create the share and it seems to work, but I'm concerned there may be an issue and I'd like to resolve it before putting the service into production. TIA!

Hi,
Your error often caused by the WinRM can’t communication to the others node, please confirm all the node “Windows Remote Management” service is running or try to disable your
firewall and AV soft then monitor it again.
More information:
WinRM (Windows Remote Management) Troubleshooting
http://blogs.technet.com/b/jonjor/archive/2009/01/09/winrm-windows-remote-management-troubleshooting.aspx
WINRM
http://blogs.msdn.com/b/powershell/archive/2007/10/30/winrm-exe.aspx
Installation and Configuration for Windows Remote Management
http://msdn.microsoft.com/en-us/library/aa384372(v=vs.85).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Issue accessing Shares via alias

Hi We have a two node file share cluster running windows 2012 r2 standard.
we have configured two aliases in DNS(Cname) to access the clustered shares. the aliases point to the host record for the cluster resource (fileserver)
i have added the aliases in the cluster parameters using :
Get-ClusterResource <resource name>|Set-ClusterParameters Aliases "Alias1,Alias2"
Below is the issue description:
Fileshares can be opened via alias 1 from all computers, irrespective of the OS.
Fileshares can be opened via Alias 2 only from windows 7 , windows 2008, windows 2008R2 and windows 2012 servers. we get an error while trying to open the shares from windows 2003 server:
"\\Sharename is not reachable . you might not have the permission to use this network resource. contact the administrator of this server to find out if you have access permissions.
Logon Failure: the target account name is incorrect."
please note: the "Alias2" which we are using was a computer added to domain earlier, which is shutdown now as the shares are migrated to the new server. we have removed its A record from DNS and replaced with Cname of the same name, but the
computer object is still present in the AD".
please help on this as we are stuck with this issue.
thanks in advance.

Hi Richik Mishra,
As far as i know, this simlar issue occured on 2012 based cluster but has fixed in 2012R2, if the legacy computer object are useless please try to delete it then try again.
The simlar issue hotfix description:
Can't access a resource that is hosted on a Windows Server 2012-based failover cluster
http://support.microsoft.com/kb/2838043
More information:
How to Configure an Alias for a Clustered SMB Share with Windows Server 2012
http://blogs.msdn.com/b/clustering/archive/2012/04/08/10291792.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Several folder shares on Windows Server 2003 R2

I have serious problems at one of our clients. They just switched from PC's to iMac's and MacBook Pro's. The backup platform is a server running Microsoft Windows Server 2003 R2 and there are several shares on this server.
Some of these shares should only be accessible by normal employees and others only to management etc.
When connecting to the shares from OSX all folders are visible even when creating a different layout with user access lists for each folder.
Is there any way of fixing this issue?
Example
Share Users - Access Everybody
Share Admin - Access Network Administrator
Share Administration - Access Management
All this worked perfectly on the Windows setup!

I have the same problem on our PC networ with PC servers. Several departments have converted to using Macs and they are able to mount to shared drives and see everything in it. My question now - is there a way to be able to access a windows shared folder for ALL USERS WITHOUT the share getting mounted on the Mac desktop?
If I created an alias of a particular Mac app or file on the Mac desktop that is stored on a Windows shared folder for all users. How can that alias work for ALL USERS without having to prompt for a uname and password and/or mounting the whole volume to the desktop?
I'm not happy with Macs running on our network but I don't have a choice on this.

Accessing a PC file server

I have a file server that I connect to to get and store stuff on. No domain, AD and that other stuff, just a username and password which enables me too see the shared folders on that machine. I notice that whenever I browse to the root of that machine in Finder (i.e. click on its icon), I get the whole "Connecting..." schpiel which takes a second or two. Once done, the browsing and copying is normal, but if I go back to the root (by clicking the back arrow in Finder), once I reach the root it will do the whole "Connecting..." thing again, thus wasting time.
Why does it do this? I have saved the username and password on my keychain. Why does it authenticate again and again in the same session?

Hi Jesper,
I would if I could, but you can't do this when the Windows 2012r2 Member Server Baseline is applied to the machine with the share. If I try to add a network location, I don't even get to the specify user name section. On the non-domain machine (the one I'm
trying to connection from), I see an error:
"The folder that you entered does not appear to be valid. Please choose another"
On the domain joined machine with the share, I see the security entry as above.
I have a feeling that the GPO responsible for this is the "Network Access: Do not allow anonymous enumeration of SAM account and Shares", which by default is disabled, but in the Baseline is enabled.
You can add to the "Network access: Shares that can be accessed anonymously"
at the Local Policy level, and although I have added the name of the share that I want the non domain machine to access, I still can't connect, so I'm obviously missing something.
Chris
PS. I CAN connect to the CA - this was just my stupidity in specifying the wrong name for the CA instance.
Chris

Use share located at server without SCCM roles

Hi,
The scenario is the following: sccm 2012 R2.
2 servers: first one is the server where sccm was installed and is DP too. Second server only is DP.
I need to deploy aditional software which source files are located at third server (without sccm roles).
Problem: When creating additional packages, I use a share located at the third server, and distribute the content to the second server (only DP role), but the package never distribute to the DP (in the sccm console I get an
error).
The question is:
It is possible to use source files located at a server without sccm roles?
Thanks in advance!

Source file access by the site server has nothing to do with the network access account.
Yes, the computer account for the site server must have access to the UNC where the source files are located -- both NTFS and share permissions (as Jörgen mentioned) There's no need to make it a local admin.
Note that the location of the source files has nothing to do with where the clients get those files from; clients always get source files from DPs.
Jason | http://blog.configmgrftw.com

Only admin can access share points.

I have OS 10.4.3 server running on a G4 xServe. It was previously running 10.2.8, but it was compromised. So I zeroed the boot drive and did a clean install of 10.4 Server and upgraded it from there. I have rebuilt all the accounts, but only my admin can access the share points from the mac's and pc's on my network. I've tried mounting them with AFP, SMB and FTP, but the server won't accept any of the user/pass combinations. It is set up as a standalone server. The only groups the other users are in are the groups I created for sharing purposes, ie. they aren't in Users or staff or anything that comes as part of the OS. Nobody, including my admin account, has a login shell, and we are all using Shadow Passwords with all of the Security options checked. The only services I have running are AFP, Firewall, FTP, Web and Windows.
Since I can log in with my admin account through SMB and AFP, I think it's a matter of not having users in the correct group. The ones that look like candidates to me are Application Server, App Server Admins, Administrators, and com.apple.accessallservices. They all seem to indicate more than file sharing access to me and I want to keep this server as bulletproof as possible. Any help would be appreciated.

Check the following:
In Server Admin, select your server, click Settings (near the bottom), then Access (near the top). Make sure that you have not restricted just one user to use the Apple File and Windows services. You should allow all users to access both of these, then prevent outside access by configuring your server's firewall.
The groups you've listed are system groups. Do not delete them and do not add users to them, or you'll have unexpected results. The Administrators group contains all administrators. By adding a user account to that group, you have made that account an administrator for the directory domain in which the account resides. (For standalone server configurations, you've made the user an administrator of the server.) The groups beginning with com.apple assist Mac OS X Server in allowing access for certain services. These are system groups that control the SACLs (service access control lists). Again, if you want to make a user an administrator or if you want to edit the SACLs, use Workgroup Manager or Server Admin.
My recommendation would be to configure your server as an Open Directory Master. You can use Server Admin to start Open Directory and set the server's role to Master. With this in place, you can use Password Server and Kerberos to authenticate users and you can back up your user database for restoration in case of a future problem. As Standalone Server, all of your users and groups are stored in the server's local NetInfo domain, so all authentication happens locally (at the server). Creating a directory domain allows authentication to take place within the domain (e.g., from the login windows of client computers).
--Gerit

Share point in server admin not working correctly... I think

I suspect that the share point in server admin is not working correctly. In workgroup manager when I click on a user and then click on the "home" tab, under the full path field I see a file path of:
afp://server.mydomain.com/Users
However if I go to Server Admin -> AFP -> Share Points then click on the Users share and then click on the share point tab below, enable auto mount is disabled. How can this be possible? I thought for a directory to show up in home in workgroup manager it had to be set as an auto mount. Has something possibly corrupted? And what?

Here's a bit more information about our setup and our experiences with Apple's CUPS implementation:
On the server, all printer queues are set up with only lpr and ipp sharing enabled with the PPD setting for each printer set to Generic Postscript. We found that setting the PPD to the printer specific one on the server caused problems when clients tried to use printer specific options, like paper tray selection, etc.. The selection would be undone, apparently because the driver on the server would override the previous settings. Using Generic Postscript allows the client PPD settings to go through unmodified. Our printers are general a mix of HP LaserJets and some Sharp Copiers.
All clients use lpd to the server queues with the printers' actual PPDs configured. Using ipp is superior in that printer feedback (jams, out of toner, etc) makes it back to the clients, but ipp only works when the client, the server, and the printer are on the same network. If the ipp client is not on the same network, the client spooler immediately goes into a paused state and the print job is stuck on the client.
Using lpd to the server queues works reliably, but there is no feedback to the client. Jobs disappear from the client queue and go to the server, appearing to the user as a successful print. If the printer is down, there's nothing they can see or do about it.

How do I install user client access licence on Windows Server 2012

I have recently setup a Windows Server 2012 Std. I have not configured any roles yet. The server licence has been installed and activated successfully. How do I get my Windows Server CAL 2012 ( tracking ID is 15 digits) onto the server. I have google
but did not get the correct result. The closest I found was
http://technet.microsoft.com/en-us/library/cc540509(v=ws.10).aspx.
I am not too familiar with the Server 2012 display so I am not certain if I am missing something. If the CALs are not captured on the server, will this restrict user access to the 2012 server?
I thank you in advance for your assistance.

Hi,
I’m glad to hear that you have found the thread as reference. As DonPick mentioned, since these are Windows Server CALs, there is no activation nor input of any kind needed. You bought the
CALs, you have the paper, you are now licensed, there is no configuration step necessary. If there is anything else I can do for you, please do not hesitate to let me know. I will be very happy to help.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Https access to Sap Content Server 620 with R/3 46C

We are trying to access the Sap Content Server 620 via Https.
We do not want to administer it via HTTPS, (as we know CSADMIN doesn't support Https in rel. 46C as for note 712332). We want to do in way that the users when do check-in/out of originals these go across the
network using Https instead Http.
According note 712330 it should be possible.
Anyone already did it ?
Any suggestions ?
NOte 506314 is not clear. We are in doubt how we applyed it.
What we did:
0)activate the SSL on the Sap COntent Server Web Site, requiring and installing a CA certificate.
1)On the R/3 server in tx OAC0 with %HTTPS filled up the
two boxes with "%HHTPS
required"
1)unpacked the Sap criptolibrary and copied all the files (including those in ntintel subdirectory created during the unpacking) under c:\Programmi\Sap\Frontend\Sapgui on a frontend PC.
2)set the env. variable SAPHTTP=c:\Programmi\Sap\Frontend\Sapgui on
Frontend PC
3) from c:\Programmi\Sap\Frontend\Sapgui we created both the SAPSSLC.pse and the SAPSSLS.pse file with the command :
3) from c:\Programmi\Sap\Frontend\Sapgui we created both the
SAPSSLC.pse and the SAPSSLS.pse file with the command :
sapgenpse get_pse -noreq -p C:\Programmi\SAP\FrontEnd\SAPgui\<PSE-NAME>
CN=localhost
4) we run the test: saphttp https://itmif069
from the frontend to the server where the Content Server is (itmif069). We recive the error:
trc file: "dev_http", trc level: 2, release: "620"
Fri Oct 08 12:26:46 2004
[2256] sccsid: @(#) $Id: //bas/620/src/krn/ftp/http.c#26 $ SAP
[2256] HTTP Start : argc - 2 a0 - saphttp
[2256] https//itmif069
[2256] SECUDIR=C:\Programmi\SAP\FrontEnd\SAPgui
<<- SapSSLSetTraceFile()==SAP_O_K
=================================================
= SSL Initialization
SapISSLComposeFilename(ssl_lib): using default "sapcrypto.dll"
SapISSLComposeFilename(server_pse): using default "SAPSSLS.pse"
SapISSLComposeFilename(client_pse): using default "SAPSSLC.pse"
SapISSLComposeFilename(anon_pse): using default "SAPSSLA.pse"
= found SAPCRYPTOLIB 5.5.5C pl16 (Jun 10 2004) MT-safe
= found SECUDIR environment variable
= using SECUDIR=C:\Programmi\SAP\FrontEnd\SAPgui
= secudessl_Create_SSL_CTX(): PSE "SAPSSLA.pse" not found,
=      using PSE "SAPSSLC.pse" as fallback
= The Server SSL_CTX
=    provides this ordered list of 9 ciphersuites:
=       1. SSL_RSA_WITH_RC4_128_SHA
=       2. SSL_RSA_WITH_RC4_128_MD5
=       3. SSL_RSA_WITH_3DES_EDE_CBC_SHA
=       4. SSL_RSA_WITH_DES_CBC_SHA
=       5. SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
=       6. SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
=       7. SSL_RSA_EXPORT_WITH_RC4_40_MD5
=       8. SSL_RSA_WITH_NULL_SHA
=       9. SSL_RSA_WITH_NULL_MD5
= Success -- SapCryptoLib SSL ready!
=================================================
<<- SapSSLInit(, read_profile=0)==SAP_O_K
ERROR => [2256] URI https//itmif069 [http.c       774]
ERROR => [2256] Connect to Host Port 443 error: NIECONN_REFUSED
[http.c       777]
We do not know if the criptolibrary ha to be instyalled to the R/3 server to.
We do not know if the CA certificate instalelled on the Sap COntent Server web site has to be installed on the R/3 server too.
Any suggestion ?
Regards

Caro Mauro,
I'm more or less in the same situation right now.
Taking into account that you ask for help on this subject last 2004 Oct. I suppose that you have probably solved the problem.
Please can you help me with the solution implemented.
Find below my current work e-mail adress
[email protected]
Thanks in advance,
Best regards, Xavier Grau.

Accessing shares on CentOS server

Similar Messages

Maybe you are looking for