Forum Replies Created
-
AuthorPosts
-
keltorsori
Participant[QUOTE][u]Quote by: guitar24t[/u][p]After replicating your configuration, I have found the solution!!! 😀
However, you won’t believe me until you try it.As a preliminary test, open system preferences > network and choose the gear-wheel icon in the bottom left and choose set service order. Drag ethernet 1 to the top and ethernet 2 right below it. Click ok then apply settings. Now verify that the server itself is able to access google.com.
Now for the REAL problem…
The problem was AGAIN the firewall, only this time BECAUSE it was off.
[code]To fix your problem, turn the firewall on and try to access the internet from the clients[/code]To me this would sound like a far-fetched fix if I had not experienced this problem myself.
If you notice any lags in services on the server, I’m sure the firewall will be the problem. I suggest using another computer, maybe running linux? 😀
Really hope this will do it for you. If you still have problems, try the gateway setup assistant to configure the firewall for DHCP and NAT.
Good luck once again,
Robert[/p][/QUOTE]As I’d tell one of my kids, “You’re a rockstar!” Turning firewall on worked. Why it worked I have no clue, but it did the job. Thanks again. With a full lab of new iMacs and being the only mac person in the district it’s nice to be able to give my kids mobile accounts and actually have all the wonders of Mac OS X server work for them.
-eric
keltorsori
ParticipantFirewall was off…
keltorsori
ParticipantI’m 90% of the way there.
I’ve got DNS, DHCP, and NAT up and running. My server has an external IP (say 10.0.1.52) and the second interface is 192.168.1.1 and is sharing the external with DHCP now over the 192.168.1.x
DNS is setup to forward all non-authorative inquiries to the external DNS. All services in and out on server work fine.The second interface goes to the WAN port on an airport base station which is setup to just forward everything on. If I associate a client computer with the airport it gets a valid IP (say 192.168.1.120) from my server. It can see my server fine (can open lab.beta.karr in safari just fine). If I use lookup to search for lab.beta.karr I get back its 192.168.1.1 address, if I reverse lookup 192.168.1.1 I get the correct domain. If I lookup google.com I get the correct info from the forwarded DNS server. Looks like everything SHOULD work fine, but now for the weird part: I can’t actually access google.com (or any external site for that matter). Lookup finds them, but no access. Even if I try the IP for google.com, no luck.
Anyone have any suggestions?
keltorsori
Participant[QUOTE][u]Quote by: guitar24t[/u][p]I’m not quite sure what you’re trying to do with it. If you tell me what you are trying to do, i.e. setup dhcp to resolve internal dns queries and still provide internet.
Just need a little bit more info. I know it’s been a while since your post, sorry.
Robert[/p][/QUOTE]Off-topic, but that’s actually exactly what I’ve been trying to do for a while. I’m not able to get an FQDN on our schools DNS, so I need to roll my own for my lab. I’ll be running DHCP and NAT. I have gotten, barely, the DNS working enough so that a query in the lab to say server.film resolves to the server, but even with forwarding on, can’t get anything outside. eth(0) is on an outside accessible static IP, eth(1) will be serving up the IP addresses to the 30 iMacs in the lab (as well as being OD master). Any chance you can help?
-
AuthorPosts
Recent Comments