Problems connecting client to shared folders (smb)

Hi, I have problems connecting Mac shared folders through VPN (PPTP)
I can access the folders in few hours but then I get error message "There was a problem connecting to the server"
The clients have Lion Version 10.8.2
The server i connect to is a 2008 R2 Server
Ping, Trace Route, Remote Desktop works
I have other Windows client connected 24/7 without any problem It's just Mac clients that are the problem with.
I do not know what else to do, any suggestions are welcome
Regards
Mathias

check the service of "OracleOraDb10g_home1TNSListener rather starts manually or automatically ?

Similar Messages

Other Macs Can't Connect To My Shared Folders...

I have 3 macbook pros in my house, all running 10.5.4 Leopard, and only one has this problem and I don't know why:
The other 2 computers can see my computer under "Shared" in the Finder, and clicking on it connects the computers successfully as "guests", but they can't see any of my shared folders. It is just empty. I am sharing my Public folder, and I have tried sharing other folders as well, but nothing will show up no matter what I try.
I can see the shared files on other computers fine, but no one can see my computers shared folders even though they can connect to my computer.
Thanks for any help...

Yes... I should add I have file sharing turned on with both AFP and SMB enabled. I also have the Firewall set to allow all incoming connections.
When the other computer connects to mine, in sharing settings, it shows one connected user connected, but that user can't see any folders on the computer no matter what I share.

Connecting to windows shared folders

I can not see any Windows PC's on our network. They do not show up in the finder? How can i find shared folders on our network using leopard?

I find it shows up in Finder, Under "shared" in a drop-down menu.

Problems connecting Client 9i from vb6

Hi, ive got an app, which connects to Oracle Client 9i from vb6 using ADO, the problem is that in some client machines i can connect with OraOleDB.Oracle.1 Provider (including mine) but in the others just got a sucessfull connection with MSDAORA provider and i dont know why..
Can anyone help me in order to use just one provider, thanks

Hello,
You must set DNS client on windows (or host name in hosts file)
regards

Problem connecting client

I'm trying to use make an application client connect to a remote server, the error message I get is this:
"Application threw an exception:javax.naming.NamingException: Serial Context failure"
The application client works of I run it on the server computer but does'nt work if I run it on a remote computer.
This is how I try to connect:
"set APPCPATH=JavaSecureClient.jar
set VMARGS=-Dorg.omg.CORBA.ORBInitialHost=servername -Dj2eelogin.name=user -Dj2eelogin.password=password
runclient -client application.ear -name ClientName -textauth"
Do any of you have any Idea why this fails?

Is your server running on a Linux machine? If it is, check the
/etc/hosts.
I had the same problem with a server on a Linux machine and the
client on a Windows XP machine. I solved the problem by changing
127.0.0.1 myHost localhost
to
127.0.0.1 localhost
<IP of myHost> myHost
in the /etc/hosts. The reason why this helps is, that in the original
constellation the InetAddress.getLocalHost() method returns the
loopback address (127.0.0.1) instead of the actual host address.
The change in /etc/hosts assures that the method returns the actual
host address.
Philip

HP Deskjet 712c Win 7 Home problem connecting to shared printer on Win XP Pro PC

Hi,
I am having a problem connecting to a shared printer on my home wireless network. The printer is HP Deskjet 712C. When I had Win XP on all my PCs, I could successfully share the printer from one PC and print to it from any PC. Worked just fine.
However, now I have 2 PCs with Win 7 Home and 1 PC with Win XP Pro. The printer is physically connected to the Win XP box. I have confirmed, on that box, it is being shared. When I try to add the printer on a Win 7 box, I select network printer and get to the point where it needs the driver. It prompts for an INF file. I have no clue where to go from there. I have done the Windows Update thing for Win 7 to update the driver list in the OS. I did see on the Win XP box that there's a place where I can load various drivers to the network for different OSs. I'm guessing that's so the appropriate drivers for those OSs will be available when adding the shared printer in those OSs. Of course, Win Vista and Win 7 are not available there. Is there any way I can share the printer from my Win XP box to my Win 7 boxes?
Also, I've tried physically connecting the printer to one of my Win 7 boxes to share it from there, but I have probems there just getting Win 7 to see the printer correctly. I'm using a Parallel - USB converter cable. When I plug it in, Win 7 sees the printer as a IEEE-1394 device instead of a printer. Even when I install the HP Deskjet 712C drivers in the OS driver list, and select the USB001 port, it tells me the printer is not plugged in, but I know it is.
I would love to hear some ideas! Please help!
Thanks

HI, I have the same issue and recently (1/15/11) posted the problem.
Did you ever figure out what was arong and get it working?

Cannot access shared folders anymore....

Hi,
We have a naughty problem at the office for accessing shared folders .
We use G5 Xserve + Xraid serving home access to 12 macs.
Our problem started when we updated all machines to 10.5.2 (nor did we have a problem with 10.5.1 or with 10.5.0).
All machines login correctly, fetch their folders with their home accesses located in the Xserve, as allways did, BUT :
·Almost all the machines running Leopard (except two) CANNOT access shared items. They get Error -5002
·The old machines running Tiger (G3 Imac's) acess shared items without problem.
So after many weeks doing multiple tests, we got the following conclusions:
·Problem is not server related.
·Problem si related to Leopard clients , although not in all
·Problem is not related to the machine, but with the account (accounts that can access shared items do it on any machine, and accounts that can't, don't do it on any machine)
·It seems that the trouble is related somewhat with Kerberos authentication, but it's not related to tickets (renewing them is no use)
·If we create new account with new name, it can access shared items
·If we create new account with same name that of the faulty one (renaming the later), it CANNOT access shared items.
We have got a problem in the office, and no clue of solving it.... Have read all over apple discussions over the internet, and although some people have similar issues, they are not as close as ours....
And none of the solutions proposed have solved the problem.
Any ideas would be greatly appreciated, cause we are starting to get desperate
Thanks everyone.

new update:
we are able to connect to remote shared folders with a different remote server (dual G4) from every machine
machines who can connect to local server are INTELs, the one who can't are PPCs
makes any sense to anyone?¿

Having trouble accessing my Macbook's Shared folders on Windows 7

After updating my Macbook to 10.10.1, My Windows 7 machine can't log in to the shared folders.
I keep getting an error: " Log in failure: unknowing username or bad password "
No settings have been changed on my Windows Machine and everything was working fine till updating my Macbook to 10.10.1
However my Macbook can still connect to the shared folders on my Windows 7 Machine....
Also I have checked the LmCompatibilityLevel on Windows and all seems okay.

Yosemite SMB from XP/Win8

Problem connecting to shared folders on Mac from Windows PCs

I am having problems using windows file sharing SMB to share folders on my Mac with windows computers on the same network. I have added a folder in 'Sharing' in System Preferences, and added a user account with SMB set to 'on', but none of the windows computers in the network seem to be able to access the address that is stated.
I can access shared folders on the windows computers from my my Mac with no problems.
Can anyone offer any advice.

I got it to work. Instead of using share\username I instead used share\short name and it connected. However, it is not very obvious from the account preferences panel how to see or modify the short name. I just read that you have to right-click the account name in the account preferences panel in order to see this. I'll give it a try soon.

Problem accessing shared folders with SMB from a Windows machine

When I reboot my Macmini, I cant access the shared folders from any Windows machine. On the Windows machine, I'm being prompted for my password, but event re-entering my password does help to get access.
The workaround I found is to go to the MacOSX System Preferences, Sharing, File Sharing, Options, and to uncheck and re-check the checkbox Share file and folders using SMB (Windows). Then I can access again the shared forders from a Windows machine and I'm not re-prompted for my password.
This is quite trooblesome to do that everytime I reboot my Mac. Is anybody experiencing the same pb? Any idea to fix it?
Also, since Lion, I'm experiencing some connection interruption, especially when copying big files from my Mac to a Windows machine.

Yes that is basically the only workaround for this problem. By chance do you have a SSD installed in the Mini?
I had this problem on my MBP when I had a SSD installed. Problem goes away with the original drive or a Seagate XT series drive.
If you don't have a SSD installed the only other option is to Wipe the drive and reinstall and test (Make a TM backup first so you can restore if the problem continues with the clean Re-Install).
JosoSG wrote:
When I reboot my Macmini, I cant access the shared folders from any Windows machine. On the Windows machine, I'm being prompted for my password, but event re-entering my password does help to get access.
The workaround I found is to go to the MacOSX System Preferences, Sharing, File Sharing, Options, and to uncheck and re-check the checkbox Share file and folders using SMB (Windows). Then I can access again the shared forders from a Windows machine and I'm not re-prompted for my password.
This is quite trooblesome to do that everytime I reboot my Mac. Is anybody experiencing the same pb? Any idea to fix it?
Also, since Lion, I'm experiencing some connection interruption, especially when copying big files from my Mac to a Windows machine.

Mountain Lion will no longer connect to my Homeserver shared folders

Yesterday I did a complete system wipe of my Mabook Pro and intalled a fresh copy of Mountain Lion, all has gone well apart from the fact that I can't connect to my Homeserver shared folders or stream from it using Plex, it can remote desktop into it though. All other devices can still connect to the server and the laptop can connect to all other just fine, any idea what might be causing this problem? Many thanks in advance.

I found if you connect to the shares themselves it's a slight work around but not ideal, so instead of doing this:
smb://servername
you do this
smb://severname/sharename
Then if you add them to your favourites by clicking the plus icon in the server connect dialogue box (⌘+k) its liveable with, hopefully this gets sorted in the next OS update.

Server 2008R2 mapping to shared folders fails users of Windows 8.1 but seems OK on Windos 8.0 and no problems for Windows 7

Having read what I could from the related questions, the answers still elude me. This issue apparently is specific to Windows 8.1.
First, a little background.
1: The server is not on a domain, The system runs Server 2008-R2 standard with all folders shared across a standard "Workgroup" type network. They would prefer to
leave this layout intact.
2: The shared folders are nothing but Data files. There are no active system folders or anything used in an "active" environment. They are mostly Word doc, excel
files, pdf, txt, etc. However, due to the requirements of the software that needs to access these files, they Must
reside on a mapped network drive letter. Nothing else works due to the way the SQL database program stores the reference points back to the data.
I have had some success using what amounts to a “simulated” mapping using WebDAV to access the server. But access speed is a lot slower ad file size is limited.
3: The system has been configured as-is for the past 3 years with Users all on Windows 7 x64 (mixed OS, some Home Premium, some Professional) and the only problems that come up are when
access is through an ISP that blocks port 445. This was the original reason for finding a WebDAV/Cloud method just for those Users since they were unable to Map drives to anything on the Office Servers from their Home Internet even when using a VPN.
When Windows 8.0 became the only version available, I added a few users whose new laptops came with 8.0 from the vendors. While there were a very few minor problems, for all practical
purposes, I was still able to provide access to the mapped folders.
As the Windows 8.1 roll-out progressed, some users were successfully upgraded while others are still stuck in Windows 8.0. The issues with this seem to be hardware related and vary
depending on the Make and model of the laptop. I have been assured that eventually all of these will be able to advance to 8.1. But this delay has given me an excellent mixed OS environment for testing.
On the users who have not yet purchased new equipment and who are still using Windows 7. There has been no change. Their drive mapping is stable and they can always connect as usual.
Those blocked from lack of port 445 or still blocked. Systems inside the Office and those with ISP's who allow port 445 can use all mapped drives as normal.
Users who had Windows 8.0 and who have not yet been able to upgrade to 8.1 also have been unaffected. Same results as Windows 7.
Users who got the Windows 8.1 upgrade as well as those that came factory loaded with Windows 8.1 seem to be a never-ending list of problems. The ones that came native with 8.1 are worst
of all. The list of error codes runs through everything that has to do with “communication with the server”. As far as I have seen, this appears to be the issue.
Whether they are in the office on a wired network connection or at home on a Wi-Fi connection, the issues have the same results but the actual error codes may vary slightly. All of
them refer back to an inability to communicate with the server.
Nothing on the server has changed in any way. Users with Windows 7 continue to have zero problems, Users with Windows 8.0 seem to be doing fine as well. Only those with Windows
8.1 are affected and their problems are dramatic with everything from a total loss of drive mapping to misdirected data when the maps are active.
I have tried to make the drives automatically remap on reboot. I have tried registry modifications. I have done everything I can think of to make a difference but the results are the same
for every system using 8.1. The mapped drive letters invariably disappear. Sometimes while the system is in use ( I think I have been able to trace this to times when the system enters Sleep or Hibernate) but always when the system reboots.
One detail that might point to somewhere is that the "time to connect" when mapping the drive is so long that I believe some of the original failures were due to not waiting for a
minimum of 3 or 4 minutes to give time for the Shares to show-up in order to map them. Once the mapping is successful, the file access speed seems normal. But invariably, the drive becomes "unmapped" repeatedly each day.
I know this was a long question but I have tried to provide every possible detail for anyone who has experienced events like this who may already have a solution. I would even be glad
to purchase a 3rd party application if that is what it takes to get this to work. My next planned effort is to try using Server 2013 but I am afraid that might open another can of worms for those who still use Windows 7.
I have also been told that this is in some way related to the push to "Cloud" support in Windows 8.1 OS but I do not see where this would come in. I can say that this was the
one place where things continued to work as before. People who had Windows 8.1 and who had to use the CLOUD copies of our data are still able to connect to it with no problems.
Any suggestions appreciated. Preferably those that would not need extensive changes to the basic network structure. This "workgroup" consists of less than 25 users and any
extreme measures would be hard to justify

Hi，
I sugget you try to ping server so that we can verify the connectivity.
Can windows 8.1 access Windows Server 2008R2?
Also,please check the event viewer to see if some error log appeared when the issue occurred.
Regards,
Kelvin Xu
TechNet Community Support

Sharing folders in 10.8.3 to windows and macs PROBLEMS

I'm tryng to share folders from an 10.8.3 imac to users in my LAN (using bot mac and windows) I'm having this problem:
1) Mac users can access the share using afp:// but
when they create new folders the permission are: drwxr-xr-x so no other can write those folders
2) PC users can access the share using smb:// but
when they create new folders the permission are: drwx------ so no other can read/write/execute
all user belong to the same group and the shared folders are owned by that group
I have create a file /etc/launchd.conf with umask 002 reboot but nothing has changed
I THOUGHT THAT MAKING SHARES IN MAC SHOULD BE EASY BUT IT SEEMS SOO HARD :-)

I'm tryng to share folders from an 10.8.3 imac to users in my LAN (using bot mac and windows) I'm having this problem:
1) Mac users can access the share using afp:// but
when they create new folders the permission are: drwxr-xr-x so no other can write those folders
2) PC users can access the share using smb:// but
when they create new folders the permission are: drwx------ so no other can read/write/execute
all user belong to the same group and the shared folders are owned by that group
I have create a file /etc/launchd.conf with umask 002 reboot but nothing has changed
I THOUGHT THAT MAKING SHARES IN MAC SHOULD BE EASY BUT IT SEEMS SOO HARD :-)

I have 2 Macs, connected to the same Wifi network. But sometimes, the shared computers does not appear on the left hand menu of the toolbar for me to access shared folders between the computers. Am I doing something wrong?

I recently bought a MacBook Air for work. Whilst at home, both my Macbooks are connected to the same Wifi network. Sometimes, the 2 Macbooks are connected and I can access the shared folders, which is great. However, every now and again, the connection seems to be lost. Is there something I need to set up so that every time both Macbooks are switched on and connected to my Wifi, it will automatically be linked?
Any help is much appreciated!

I have found with AppleTV that it is the IPV6 on the computer you want to access is the problem. The issue is that Homegroup on Win 7 or Win 8 requires IPV6 to work, but AppleTV won't work with IPV6. (So maybe double check you have IPV6 turned off)
So you have to make a choice - Homegroup or AppleTV.... but you can't have both, until Apple brings ATV up to date. (crazy that it does not recognise IPV6 - c'mon Apple!)
You can set up sharing individually in Win 7 or 8 and have the ATV access files that way.
Having said that, there is always the exception.. I have an old HP home server running Win8 and it services ATV - but is part of the Homegroup... have no idea why it works on both, but no other machine on the home network will talk to both ATV and Homegroup at the same time!

Open Directory and connection to shared folders fail

Hi,
For testing i've setup an Open Directory Master (Leopard server 10.5.2) with shared folders and portable home directories.
Login and synhronizing works as it should. But once logged in, when i click on the server in finder i just get connection failed. When i choose "connect as" and log in as the same user and password as authenticated at the login to the computer (authenticated to OD) it works.
I thought it should work like a single sign on?
Any clues?

Hi
If you browse the discussion forum you should find this:
http://discussions.apple.com/thread.jspa?threadID=1251475&tstart=0
Basically browsing using the Finder or Side Panel does not work well or breaks easily (as far as I can tell it has been like this since 10.2). In an OD environment trying to connect and getting a ticket using that method will probably fail. The workaround - or the 'fix' - is to use 'Connect to Server' from the Go Menu using the Server's IP address. In my experience it does not seem to matter whether AFP is set to Kerberos, Any or Standard for the authentication method. It also does not seem to matter whether the Server is configured in Standard or Advanced.
I've not come across anything yet regarding Workgroup. Probably in that configuration it may not be an issue as this mode - as far as I can see - is ideal for AD-OD integration. In that environment OSX Server would not be the KDC and mac clients will be using the AD for SSO.
Since this has been happening since 10.2 I don't see Apple addressing this anytime soon, however you never know?
Tony

Problems connecting client to shared folders (smb)

Similar Messages

Maybe you are looking for