Netgear DG834N and Leopard Server VPN

Has anyone had the Netgear DG834N up and running with Leopard Server's VPN service?
I've had it recommended to me by someone who has been using for VPN and Tiger Server.

Well, I have now. Works just fine.

Similar Messages

DrayTek Vigor 120 and Leopard Server VPN

Does anyone successfully use the DrayTek Vigor 120 (UK) with Leopard Server's VPN? Can't find any explicit support of VPN pass-through.

Hello, I got this VPN working with a 2820 draytek.. Where the draytek is allowing pass though to a mac os server. FYI, sometimes the first connect fails (timeout) but the second connect always works and the first usually does but...
Here are some screen shots for you to download as it is easier to see what to allow for firewall configuration than describing it... This link has a series of screenshots that make it very clear..
http://www.getdropbox.com/gallery/617466/1/Apple%20Discussion%20Links?h=208a6f
or
http://tinyurl.com/mhph27
Message was edited by: ColoradoMan

Remote Desktop and Leopard Server VPN

We have remote users logging into our server via VPN PPTP, they login fine and get the relevent address's but once there we can't see or connect to the using ARD 3.2.2. We can control the Server over the internet but not over VPN any ideas greatly appreciated.

We have now got the situation that we can control the server over the VPN using screen sharing from another Leopard Mac but still can't control in the other direction.

Snow Leopard Server VPN and other Servers

I am thinking of deploying Snow Leopard Server at work using the Mac MiniServer option. We have a few Macs that we would like to manage their settings with. We also have Active Directory. I plan to use Open Directory with the Mac then use kerbos for logins.
My question is if I use the Snow Leopard Server VPN with the Macs, will the users be able to access other resources on the LAN like Active Directory Shares, Exchange, and internal Intranets? Or only the Snow Leopard Server?
Thanks,
WillGonz

It sounds like you will have 2 different kerberos realms, one in OD and one in AD.
If you want them to use the same realm (the AD one) you need to look at a "golden triangle" setup.
If you want to authenticate the VPN connection using Kerberos I suspect you need to be able to reach the KDC server from Internet before the VPN is up. That would mean it needs to have a public IP and same name as on the LAN(?).
As an alternative a Radius connection for the VPN authentication from the Mac to an AD/Radius server might be possible.

Can you help me solve my Leopard Server VPN madness?

Hello all,
I've been having a devil of a time getting Leopard Server's VPN service to work "properly". None of this is mission critical, as it's simply on a home system I'm using as a nat/dns/dhcp/firewall/mail/web server for my Comcast line (with a static IP). But, it is frustrating, because I currently have a 10.4.11 Server fulfilling the same roll. So it seems like Leopard should be able to be made to work. I'm gonna go step by step here with my install process in the hopes that if I'm doing something wrong someone will be kind enough to catch it. Thanks for bearing with me.
I've installed Leopard Server 10.5 (Mirror door G4, FYI) with the built-in ethernet connected to my Comcast router (with a static external IP). Immediately after 10.5 installs I restart and update everything to 10.5.2, then I install a Sonnet Gigabit NIC, it's drivers, and assign it 192.168.3.1, where it will live as my internal router, server, etc. I turn on DNS and setup an internal ".lan" zone that resolves to 192.168.3.1. Pop into Terminal and confirm that rDNS is in fact working, it is. And check that "changeip -checkhostname" resolves itself correctly (to the external IP).
Next, turn on the NAT service and run the gateway setup assistant. After a reboot I quickly check that my internal clients with static IPs (192.168.3.10, .20, etc) are working and pulling DNS OK, they are. Jump into the Firewall, and for the moment just open it wide up by accepting all connections. At various times during testing I've configured the firewall to exactly match my 10.4 Server firewall, but for the time being I can just leave it open. I create a Firewall group to cover my 192.168.3.x internal network, and another to handle 192.168.3.60/29 to handle the VPN service I'll setup in a sec. Jump over to the DHCP service where by default gateway setup creates a 192.168.1.x DHCP zone. I delete that and create a new 192.168.3.x zone covering .50-.59. Turn DHCP on and confirm it's working, good, it is.
Now, here is where the VPN fun begins. The last service I turn on is the VPN service (I've alternatively tried letting Gateway Setup activate it, and just doing it myself, with this same result). I configure it to accept L2TP at 192.168.3.60 - .63. Like I said this is a home server, so I don't need a lot of VPN connections. Finally, when I test the VPN from a 10.5.2 Client (MacBook coming in off a neighbors open wireless network with a 10.0.0.x string) I am able to connect, and I can see/ping/mount/share screen on the server. I can also ping the attached VPN client at 192.168.3.60 from the server. However, I cannot ping or see (In ARD) any other machines on the internal network from the attached VPN client. Likewise from one of the internal systems, say my Mac mini at 192.168.3.10 I cannot ping the attached VPN client at 192.168.3.60. Out of curiosity I've tried doing a rDNS lookup while attached to the VPN and the client isn't able to resolve any of the internal DNS entries.
So, what gives? As I've mentioned I have exactly this same setup working just fine with Tiger Server. Same NAT, same Firewall, same DNS, and same L2TP VPN setup. For the life of me though, I cannot get attached VPN clients to see the internal network when I put Leopard Server in place. Clearly the internal DNS isn't working for attached VPN clients, although I'm not certain if that is a cause or a symptom. I've setup a network routing definition for the internal private network, which didn't help. I also tried setting up PPTP instead of L2TP, and had the same problem.
Is anyone having similar problems with Leopard Server's VPN service? If not, could someone hit me with the clue stick and set me right? As I said, in the grand scheme of things this isn't a big deal for me. But, it's just frustrating that I can get so close to updating my home server and just fall short.
Thanks!

Your post actually contains the Key to solve the problem and there is not really a big need for going all the way to use the Property List Editor to fork around /etc/ipfilter/ipaddressgroups.plist.
There has been much written on this problem but basically you see that most is trial and error and this does include myself and my findings in this post, too, but I think I can further narrow down on what CAUSES this problem and how to fix it.
First off, we are talking a combination of using NAT (Network Address Translation - bridging an Internet connection on an external network card over to an internal network card), Firewall (which is needed in OS X to be have NAT working because the Firewall "helps" NAT by doing its job, DHCP (for providing dynamic IP addresses to clients on the internal network, don't confuse, DHCP is not providing this service to the VPN clients, that is done by the VPN server), and - last but not least - VPN to provide access to not only to the server but to any machine on the internal network over the outside network card (aka, giving remote clients a chance to connect to the local network over the public Internet in a save and nice way).
OK. The short story: you can do it ALL in Mac OS X 10.5's Server Admin tool. If it fails it is nearly always the Firewall!
You can check if this is the case for your setup by temporarily opening the Firewall up to not block any traffic: in Server Admin, click on Firewall -> Settings -> Services -> Edit Service for: any and click "Allow all trafic from "any"", save it (and to be 100% sure, stop and restart the firewall. If your clients can NOW connect at least to the server, it was the firewall. Now don't forget to switch off allowing all traffic from any, or you will be left with an open doors server ready for anybody to explore
Now what goes wrong in the first place? It appears that the GSA (Gateway Setup Assistant) that is "hidden away" in the NAT settings does something awfully wrong. It will set up all the address groups in the firewall: the any group will remain as it is usually, another one defining the internal network, and a one called VPN-net for VPN.
What it DOES do wrong here (I am no firewall expert, this is purely trial and error, so please anybody do explain!) is to give the VPN-net exactly the same address range as the internal network. And here seems to be the overall problem.
When Twintails wrote to add 192.168.3.60/27 as address range for VPN, I realized what he/she did. Writing 192.168.3.60/27 effectively narrows down the address range starting at 192.168.3.33 up to 192.168.3.62. There are millions of subnetmask calculators out on the net, give it a try e.g. here: http://www.subnet-calculator.com/
So, I looked for what range of address will actually be given out by the VPN server to VPN clients upon connections. Of course you need to make sure that this address range is NOT given out by your DHCP server.
In my setup, the server is 192.168.1.1, the DHCP server provides addresses from 192.168.1.10 up to 192.168.1.127 (I start with 10 because I have some static addresses for special purposes from 192.168.1.2 to 192.168.1.9. So, this means, anything above 192.168.1.127 is potentially "free" for my VPN connections.
Next I used the subnetmask calculator to find a narrow address group that matched my purposes. I found 192.168.1.192/26 which effectively gives me a range from 192.168.1.192 to 192.168.1.255 (which is in fact more then I have clients connecting from externally!).
I went to the Server Admin Tool, and clicked Firewall -> Settings -> Address Group and edited the VPN-net one. First I deleted what was in "Addresses in group" and entered from scratch 192.168.1.192/26. Next - just to make certain because basically this is what Twintails had in his/her post by saying to add a name String with exactly the same information - I overwrote VPN-net by 192.168.1.192/26 and saved. (I THINK that this last step might not really be needed, but I haven't tried).
Next click Save (basically it should already work, but I always want to be extra sure, so I stoped and immediately thereafter started the firewall again to be 100% certain all new rules are now active.
And now: it works! Clients can access the server AND the entire local network from remote using VPN.
One last comment: I have the feeling that (although less safe and less advanced technologicall) PPTP works much better for us then L2TP. So I have switched off L2TP support altogether because it simply NEVER really worked. We are using Mac OS X 10.4 and 10.5 to connect to the 10.5 server using this setup.

Leopard server VPN performance

What kind of a performance do you get with Leopard VPN server?

Over the Internet or locally (between subnets)?
When VPN maximum perfomance/throughput for a device is stated by a hardware VPN router/firewall manufacturer, it must be by measuring the throughput through the device "locally", for example from WAN to LAN, when no other traffic is passing through the device. How well it performs encrypting/decrypting (the hardest part) and then moving the packets between interfaces must mostly be a device CPU dependant figure.
But if you mean connecting through the Internet from a DSL connection I would expect no real difference between the Juniper and OS X server VPN. It would most likely not be the server that is the restricting factor.
But of course depending on what hardware a VPN router it is running on and if or not taxed heavily by running other services simultaneously, what other traffic is passing to and from Internet at/between both sides (if the "road" is congested), available bandwidth on the client and/or server Internet connection and other things (firewall under attack), performance varies over time.

Leopard Server VPN L2TP Not receiving connections, PPTP works fine??

All,
Setting up a new OSX Snow Leopard server. The server is NOT running the firewall service. I created an L2TP VPN, with PPTP. PPTP works fine... however I am unable to connect to the L2TP.
I receive the error: The L2TP-VPN server did not respond. Try reconnecting, if the problem continues, verify your settings.
The server is behind an apple airport N router. I've tried connecting from both inside and outside (outside I mapped ports UDP 1701, 4500, and 500) with no luck. I even tried creating a VPN connection from the actual server to itself, and get the same error.
The logs show nothing - The extension is loaded, listening for connections, and nothing at all after that even after a connection try is made. PPTP works fine, and lots of logs there.
Appreciate any help!!

I too since yesterday am having the same issue. It's as if the L2TP tunnel is not making it thru the Airport N DualWireless to the MacMini server. It was running just fine up until yesterday when I installed Security Update 2010-001 v1.0. I can use PPTP outside my network all day long and I can even use L2TP from inside my network just fine so I know the server is responding to local requests. I have tried from cell modem, client T1, client cable internet with no joy. I have rebooted AEBS & Server with no results. When trying L2TP from outside LAN and watching log in realtime it does not even show it's trying. I had this issue once before when I had mobileme "back to my mac" turned on and it was causing an issue but it's off and hasn't been on in some time. I suspect the update. Did you install that update?

IPod Touch and Leopard Server network

At school we have staff and students beginning to explore iPod Touches as a classroom resource. There is no problem getting them to use the school's AirPort network, but some apps, such as Google Earth will not run.
I'm wondering if anyone has experience of using iPod touches in a Leopard Server environment and if they have any tips or hints to share please?
Brian Bowell
ICT Support
Berkley School
Hamilton
New Zealand

Hi Brian,
You really should have to do anything specific on your network to make the touch work with Leopard Server. Here are a few questions to point you in the right direction:
Are you seeing any specific error messages?
Are you blocking any ports on your network?
Have you looked at the log files from a device that is exhibiting this behavior?
Good luck,
Jon

Netgear DG834N and Airport Express

I have a network set up on my Netgear DG834N wireless router/modem. Can I 'add' an Airport Express base station to the same network and play iTunes through my speakers? At the moment it's on it's own network and that is far from ideal.
thanks
Jeff

Welcome!
Open Hard Drive > Applications > Utilities > Airport Utility
Click on your AirPort Express and there is a guided step by step to walk you through the process.
Basically, you want to "join" the network that the Netgear is creating by selecting the name of the network, security and passord. iTunes is enabled by default. You will need to assign a name to your Express and a device password, etc.
Post back if you need more information.
The Setup Guide may help as well.

Netgear dg834n and 802.11n

Does anyone know if it is possible to use a MacBook Pro C2D 2.16 GHz to a Netgear dg834n via 802.11n?
Is there any compatibility issue?
My connection is fine, but only with 802.11g standard.
Thanks.

When the iPhone joins the 802.11n (b/g compatible network) in the 2.4GHz band, the network will drop down the speed a little to deal with the slower device (this is done automatically, you don't have to manually change it).
Alternatively, you can manually switch between 5GHz 802.11n and 2.4GHz b/g mode every time your iphone need to connect to the internet. But it's a lot of inconvenience.
The best way is to run all 802.11n devices in 5 GHz band, and your iPhone in a separate 802.11b/g 2.4 GHz band network. But this requires two base stations.
From your earlier post, I don't think you have two base stations needed to set up a dual-band network, and you will need to purchase additional new base station to set this up.

Vanishing files Vectorworks 12 and Leopard Server 10.5.6

We have a Server installed with Leopard Server version 10.5.6 We are using Vectorworks 12.0.1 (CAD programme). When a user connected to the server working on a drawing goes to save the drawing it saves then displays an error message saying it cannot save. When you go to the directory where the file used to live it has vanished.
This problem does not happen all the time just when the machine feels like it.

The first thing you might want to try is patching VectorWorks to the last version of 12, which was 12.5.3. Since version 12 came out before Leopard, I know that Nemetschek had a number of problems that had to be patched. We had already upgraded to VW2008, so we didn't have to deal with any of that.

Time Machine and Leopard Server

I'm trying to verify the Time Machine works on Leopard Server sufficiently enough to be a reasonable backup vehicle for the Leopard Server to an external backup drive, for example.
I have read many posts where Leopard Server can act as a Time Machine Server for workstations, but my main interest is in using Time Machine, running on the Leopard Server to back up that Server.
My guess is that it will?
Thanks in advance for everyone's input.

Timemachine is not supported for "ADVANCED" Server set up but the SIMPLER setups YES. There are also settings for backing up network computers as well as backing up the server.
Supposed in Advanced not all system files are backed up. There are a number of threads regarding this in the Server section of the discussions.

Xgrid and Leopard Server

Is Leopard Server required on the Xgrid controller or can the controller be running Leopard client?

The controller can be using the client version of Leopard; click here for more information.
(41636)

Snow Leopard Server VPN and Android Client

Hi
I have a VPN which works absolutely fine with various (Apple) products. However, I have never managerd to get an Android device to connect to the VPN. Would anyone have any clue as to how to work around this?
FWIW, the VPN is set up to use L2TP over IPSec with a shared secret. The gateway firewall is set up to allow pass through for VPN protocols and the appropriate ports have been mapped to the server. The system works fine for Macbooks of various flavours, iPod, iPad and I believe it's been tested with a Windows box (may have turned on PPTP for that. Can't remember). All this points to a flaw in the Android VPN client - which seems to be something of a known issue but beyond my understanding.
With the above in mind, anyone got a sensible work around (other than the daft suggestion that someone will inevitably make wrt buying an iPhone)?
TIA
Simon

Fat Freddie, we're thrilled you got it working on your Nexus 7, would you care to share HOW you got it up and working? What were the server settings. I'm trying to get it setup on a Nexus 4 running 4.2.1, and it is getting the same LCP timeout in the logs that the poster "l4r5" was reporting.
Did you get this and solve it?
Here are my config settings:
vpn:vpnHost = ""
vpn:Servers:com.apple.ppp.pptp:Server:Logfile = "/var/log/ppp/vpnd.log"
vpn:Servers:com.apple.ppp.pptp:Server:VerboseLogging = 1
vpn:Servers:com.apple.ppp.pptp:Server:MaximumSessions = 128
vpn:Servers:com.apple.ppp.pptp:DNS:OfferedSearchDomains:_array_index:0 = "home"
vpn:Servers:com.apple.ppp.pptp:DNS:OfferedServerAddresses:_array_index:0 = "192.168.1.1"
vpn:Servers:com.apple.ppp.pptp:DNS:OfferedServerAddresses:_array_index:1 = "<redacted>"
vpn:Servers:com.apple.ppp.pptp:DNS:OfferedServerAddresses:_array_index:2 = "192.168.1.11"
vpn:Servers:com.apple.ppp.pptp:Radius:Servers:_array_index:0:SharedSecret = "1"
vpn:Servers:com.apple.ppp.pptp:Radius:Servers:_array_index:0:Address = "1.1.1.1"
vpn:Servers:com.apple.ppp.pptp:Radius:Servers:_array_index:1:SharedSecret = "2"
vpn:Servers:com.apple.ppp.pptp:Radius:Servers:_array_index:1:Address = "2.2.2.2"
vpn:Servers:com.apple.ppp.pptp:enabled = yes
vpn:Servers:com.apple.ppp.pptp:Interface:SubType = "PPTP"
vpn:Servers:com.apple.ppp.pptp:Interface:Type = "PPP"
vpn:Servers:com.apple.ppp.pptp:PPP:LCPEchoFailure = 5
vpn:Servers:com.apple.ppp.pptp:PPP:DisconnectOnIdle = 1
vpn:Servers:com.apple.ppp.pptp:PPP:AuthenticatorEAPPlugins:_array_index:0 = "EAP-RSA"
vpn:Servers:com.apple.ppp.pptp:PPP:AuthenticatorACLPlugins:_array_index:0 = "DSACL"
vpn:Servers:com.apple.ppp.pptp:PPP:CCPEnabled = 1
vpn:Servers:com.apple.ppp.pptp:PPP:IPCPCompressionVJ = 0
vpn:Servers:com.apple.ppp.pptp:PPP:ACSPEnabled = 1
vpn:Servers:com.apple.ppp.pptp:PPP:LCPEchoEnabled = 1
vpn:Servers:com.apple.ppp.pptp:PPP:LCPEchoInterval = 60
vpn:Servers:com.apple.ppp.pptp:PPP:MPPEKeySize128 = 1
vpn:Servers:com.apple.ppp.pptp:PPP:AuthenticatorProtocol:_array_index:0 = "MSCHAP2"
vpn:Servers:com.apple.ppp.pptp:PPP:MPPEKeySize40 = 0
vpn:Servers:com.apple.ppp.pptp:PPP:AuthenticatorPlugins:_array_index:0 = "DSAuth"
vpn:Servers:com.apple.ppp.pptp:PPP:Logfile = "/var/log/ppp/vpnd.log"
vpn:Servers:com.apple.ppp.pptp:PPP:VerboseLogging = 1
vpn:Servers:com.apple.ppp.pptp:PPP:DisconnectOnIdleTimer = 7200
vpn:Servers:com.apple.ppp.pptp:PPP:CCPProtocols:_array_index:0 = "MPPE"
vpn:Servers:com.apple.ppp.pptp:IPv4:ConfigMethod = "Manual"
vpn:Servers:com.apple.ppp.pptp:IPv4:DestAddressRanges:_array_index:0 = "192.168.1.240"
vpn:Servers:com.apple.ppp.pptp:IPv4:DestAddressRanges:_array_index:1 = "192.168.1.254"
vpn:Servers:com.apple.ppp.pptp:IPv4:OfferedRouteAddresses = _empty_array
vpn:Servers:com.apple.ppp.pptp:IPv4:OfferedRouteTypes = _empty_array
vpn:Servers:com.apple.ppp.pptp:IPv4:OfferedRouteMasks = _empty_array
vpn:Servers:com.apple.ppp.l2tp:Server:LoadBalancingAddress = "1.2.3.4"
vpn:Servers:com.apple.ppp.l2tp:Server:MaximumSessions = 128
vpn:Servers:com.apple.ppp.l2tp:Server:LoadBalancingEnabled = 0
vpn:Servers:com.apple.ppp.l2tp:Server:Logfile = "/var/log/ppp/vpnd.log"
vpn:Servers:com.apple.ppp.l2tp:Server:VerboseLogging = 1
vpn:Servers:com.apple.ppp.l2tp:DNS:OfferedSearchDomains:_array_index:0 = "home"
vpn:Servers:com.apple.ppp.l2tp:DNS:OfferedServerAddresses:_array_index:0 = "192.168.1.1"
vpn:Servers:com.apple.ppp.l2tp:DNS:OfferedServerAddresses:_array_index:1 = "<redacted>"
vpn:Servers:com.apple.ppp.l2tp:DNS:OfferedServerAddresses:_array_index:2 = "192.168.1.11"
vpn:Servers:com.apple.ppp.l2tp:Radius:Servers:_array_index:0:SharedSecret = "1"
vpn:Servers:com.apple.ppp.l2tp:Radius:Servers:_array_index:0:Address = "1.1.1.1"
vpn:Servers:com.apple.ppp.l2tp:Radius:Servers:_array_index:1:SharedSecret = "2"
vpn:Servers:com.apple.ppp.l2tp:Radius:Servers:_array_index:1:Address = "2.2.2.2"
vpn:Servers:com.apple.ppp.l2tp:enabled = yes
vpn:Servers:com.apple.ppp.l2tp:Interface:SubType = "L2TP"
vpn:Servers:com.apple.ppp.l2tp:Interface:Type = "PPP"
vpn:Servers:com.apple.ppp.l2tp:PPP:LCPEchoFailure = 5
vpn:Servers:com.apple.ppp.l2tp:PPP:DisconnectOnIdle = 1
vpn:Servers:com.apple.ppp.l2tp:PPP:AuthenticatorEAPPlugins:_array_index:0 = "EAP-KRB"
vpn:Servers:com.apple.ppp.l2tp:PPP:AuthenticatorACLPlugins:_array_index:0 = "DSACL"
vpn:Servers:com.apple.ppp.l2tp:PPP:VerboseLogging = 1
vpn:Servers:com.apple.ppp.l2tp:PPP:IPCPCompressionVJ = 0
vpn:Servers:com.apple.ppp.l2tp:PPP:ACSPEnabled = 1
vpn:Servers:com.apple.ppp.l2tp:PPP:LCPEchoInterval = 60
vpn:Servers:com.apple.ppp.l2tp:PPP:LCPEchoEnabled = 1
vpn:Servers:com.apple.ppp.l2tp:PPP:AuthenticatorProtocol:_array_index:0 = "MSCHAP2"
vpn:Servers:com.apple.ppp.l2tp:PPP:AuthenticatorPlugins:_array_index:0 = "DSAuth"
vpn:Servers:com.apple.ppp.l2tp:PPP:Logfile = "/var/log/ppp/vpnd.log"
vpn:Servers:com.apple.ppp.l2tp:PPP:DisconnectOnIdleTimer = 7200
vpn:Servers:com.apple.ppp.l2tp:IPSec:SharedSecretEncryption = "Keychain"
vpn:Servers:com.apple.ppp.l2tp:IPSec:LocalIdentifier = ""
vpn:Servers:com.apple.ppp.l2tp:IPSec:SharedSecret = "com.apple.ppp.l2tp"
vpn:Servers:com.apple.ppp.l2tp:IPSec:AuthenticationMethod = "SharedSecret"
vpn:Servers:com.apple.ppp.l2tp:IPSec:RemoteIdentifier = ""
vpn:Servers:com.apple.ppp.l2tp:IPSec:IdentifierVerification = "None"
vpn:Servers:com.apple.ppp.l2tp:IPSec:LocalCertificate = "<>"
vpn:Servers:com.apple.ppp.l2tp:IPv4:ConfigMethod = "Manual"
vpn:Servers:com.apple.ppp.l2tp:IPv4:DestAddressRanges:_array_index:0 = "192.168.1.224"
vpn:Servers:com.apple.ppp.l2tp:IPv4:DestAddressRanges:_array_index:1 = "192.168.1.239"
vpn:Servers:com.apple.ppp.l2tp:IPv4:OfferedRouteAddresses = _empty_array
vpn:Servers:com.apple.ppp.l2tp:IPv4:OfferedRouteTypes = _empty_array
vpn:Servers:com.apple.ppp.l2tp:IPv4:OfferedRouteMasks = _empty_array
vpn:Servers:com.apple.ppp.l2tp:L2TP:Transport = "IPSec"
Can you see any discrepancy?
Thanks in advance.

WGM vs Server Admin and Leopard server access

I am able to access my Leopard xserve through my firewall using Server Admin tool, but not when I try with WGM.Message is..."host unknown" ...."host unreachable." What is the difference? Not a problem with ARD either ....mmmmm. Can someone shed some light on the experience? Thanks, J Langloi

By filtering, (if I may), he meant restricting. IE: If you're going to do this, you absolutely need to have the Firewall restrict what external IPs are allowed access, rather than making those ports wide open to anyone and everyone.
But, it's pretty much industry-standard/ standard-practice to disallow connections across a company firewall to internal servers, except via VPN. (And by this I am excluding servers that are intended to be public-facing but are still appropriately firewalled).
In rare cases where VPN is not a readily-available option, it is possible to connect to both Server Admin and Workgroup Manager over ssh, but I don't suggest going that route without absolutely securing ssh in every possible way (has minor typos I wish I could fix but nothing that confuses the vital info): http://discussions.apple.com/thread.jspa?messageID=7082312

Netgear DG834N and Leopard Server VPN

Similar Messages

Maybe you are looking for