I will also follow up on the DNS suggestion. I don't think our IT guys have touched the client. I've been using the same VPN client on two different PC laptops for the last 5 years. I don't think my company modifies our VPN clients, but I will follow up on this to be sure. For what its worth, I tested several connections while directly connected to the LAN via ethernet at work today. My MBP isn't "seeing" any SMB servers on the network. I think I was attempting to map my drives wrong. So what I mentioned earlier about losing my network no longer seems to be an issue. The connection with my Apani client has stabilized. I haven't been able to find much support for this on the internet so I really appreciate it. I had thought about getting a Cisco VPN client working on my Mac, but went the Virtual Machine route instead. I'm running a somewhat different setup than you in that I'm running Windows XP Virtual Machines on my Mac and they are establishing the VPN connections that I need.
Substitute the actual IP address of the server in the 2nd example. Your entry in the connect dialog box should look something like these You should get a list of SMB servers that the mac "sees" on the network.įor SMB Shared Drives, I think you have to specify a valid share, not sure if just the server name will work. Open Terminal, type findsmb and hit return. There is something else you can try to see if your Mac is seeing any shares. If you are getting messages to the effect it can't find the server, then you might be having DNS issues when on the VPN. Some larger companies modify the VPN clients they get from the vendor, so if you're trying to access with a plain vanilla Mac version and they have modified the PC version this probably isn't going to work. I can't help you with why the VPN connection may be dropping. When I connect my MBP at work (ethernet) everything works fine. I can't browse the server because "connect to server" doesn't see anything. I am able to ping the destination IP address that Apani gives me. Perhaps I'm setting this up wrong? I get an error code -36 (can't complete this operation because some data in "afp://smb%5C%5Cxxxx-fs02" could not be read or written. I did notice that "connect to server" automatically defaults to afp://smb:\\xxxx-fs02. All of this works with the PC, but I can't set up my MBP to do it.
I could use smb:\\xxxx-fs02\Vol3 to get to a specific drive, but it shouldn't matter. I try to "connect to server" using smb:\\xxxxx-fs02 where xxxx-fs02 is the server. When I use the PC, I simply connect via VPN and access our network drives (which are mapped). I normally use my work-provided laptop to work from home. I have obtained the proper security settings and I am able to establish a successful connection.
0 kommentar(er)
