Releasing unused DHCP IP addresses in OSX Server 10.4

In OSX Server 10.4.11 is there any way to release unused DHCP client addresses in the Server Admin app? We have 73 clients showing (and only 30 on the network) because various computers have been added to the network and removed/reinstalled at various times, and that means we're running out of available addresses in our little chunk of the subnet.
We've previously set a longish lease time on DHCP addresses because we've had problems in the past with sleeping Macs being woken up and having clashing IPs with other Macs that have had that IP reassigned to them, but it means that we do have a long list of unused DHCP clients.
Does Server 10.5/10.6 allow the release of DHCP addresses from the admin app (oh, for a right-click delete!), or is that just not possible in the DHCP protocol (NB I'm trying to release unused IP addresses, not asking live clients to rescind their IP address).

It's not legal within the DHCP protocol - as far as the server is concerned, that IP address has been handed to the client and should be reserved for that client until the lease expires. The server has no way of knowing whether the client is still using the address.
You may be able to break the rules, though - the server stores the DHCP leases in /var/db/dhcpd_leases, so you should be able to stop the DHCP server, edit the file to remove the unnecessary leases, then start the server back up. No guarantees, tho'.

Similar Messages

Adding Bootp/DHCP Options to Mac OSX Server 10.4

Our telephone supplier - Splicecom (http://www.splicecom.com/) - has asked us to ensure that option 66 and option 67 are enabled in order for their PCS400 handset to pick up an IP address from our Mac OSX Server DHCP server.
Please can somebody advise on how to either:-
a) ensure that they are already enabled
or
b) tell me how to enable them
Many thanks
Paul

I think you need some other DHCP server to acheive what you need
option #66 = Boot Server Host Name
option #67 = BootFile Name
(Try "man bootpd" in Terminal.)
The ISC DHCP server can be installed in OS X using PortAuthority / DarwinPorts:
"dhcp 3.0.3, Revision 1, net/dhcp (Variants: darwin_8)
http://www.isc.org/products/DHCP/
ISC's Dynamic Host Configuration Protocol Distribution reference implementation of all aspects of the DHCP protocol, through a suite of DHCP tools: A DHCP server, client, and relay agent. These tools all use a modular API which is designed to be sufficently general that can easily be made to work on POSIX- compliant operating systems and also non-POSIX systems like Windows NT and MacOS. The DHCP server, client and relay agent are provided both as reference implementations of the protocol and as working, fully-features sample implementations. Both the client and the server provide functionality that, while not strictly required by the protocol, is very useful in practice. The DHCP server also makes allowance for non-compliant clients which one might still like to support.
Platforms: darwin
Maintainers: [email protected]"
But you'll need to configure this DHCP using a texteditor.

How to setup default gateway in a DHCP client. The default gateway will be the Ip address of the server that has RRAS installed, hence routing cabalities.

How to setup default gateway in a DHCP client. The default gateway will be the Ip address of the server that has RRAS installed, hence routing cabalities.

Hi Bill,
Thank you for replying back...Yes, I was actually asking how do you set the default gateway address on the DHCP server?,
I believe I got the answer below:
To configure the DHCP default gateway option Click Start, point to Administrative Tools and then click DHCP. In the console tree, expand the applicable DHCP server, expand IPv4, and then right-click Scope Options Click Configure Options, check 003
Router, type the applicable Server name and IP address, and then click OK.
Thank you

Set up airport express for osx server

Hello,
This is my first post, im not a specialist, so hope to give the correct info.
I have a Speedtouch 530 (dsl modem) that is connected to an airport express. This is used to connect both a Macbook and iMac via wifi. Then I have upgraded the iMac to osx server, bc i would like to use is to share folder and wiki's on the web. My isp has also granted a fixed ip.
I would like to use this speedtouch in bridge mode in order to use the airport express as router. But i've been reading and trying for 2 weeks now, and the result is that i'm happy to be back online. But is still dont have a clue how to configure these things to get this server running.
Any help is appreciated, Benjamin

Hello Tesserax,
Thank you for your interest in this problem
Its the combination of both i think. In the speedtouch under: home netmetwork>devices>Assign the public IP address of a connection to a device. But then i get this message:
(1) release the current private ip address of this device.
(2) renew the ip address of this device in order to aquire the public ip address
after that i cant open the speedtouch any more (http://192.168.0.1) but the airport still recognizes it.
Also in the manual of osx server they say not to use a standard IP pool (to avoid double use this computers that want to log in). Do i have to change these IP before assigning the public IP to the airport express?
So i'd like to set the range to 10.0.8. and the speedtouch on exp 10.0.8.1
(Home > Home Network > Interfaces > LocalNetwork>configure>add IP>10.0.8.1 & 255.255.255.0) then later when trying to configure the airport pool of DHCP i get an start and ending error.
Another question, is it best to assign the public ip directly to the iMac or best to the airport?
Benjamin

File locking with OSX Server & Microsoft Word

We have a small office LAN based on a Airport Extreme bases station. Periodically Microsoft Word reports a break in connection to the shared folder where we store documents to get disconnected. When that happens and the user reconnects to the share, the user gets the file read-only message for the Word document that was open at the time.
I have found that in order to clear the read-only flag, I have to restart the server and open the Word file on the server with the ID of the user who was editing the file on the remote computer. Only that seems to clear the file locking that causes the file to be read-only.
I cannot figure out a less drastic way to release the lock file. I don't see any hidden temp files in the same folder as the document that is locked for editing found by ls -a or in the root direction of the shared folder in the .TemporaryItems/folders.<UID> that seems to be holding the lock.
I have run chflags nouchg <Word file> from Terminal, but that seems to have no effect either. I also used xattr to see if there were any locks held that way, but I don't see anything that way either.
File sharing to Macs only, which are configured just to use AFP through OSX Server.
Does anyone understand how the file locks of Word documents can be released directly with out restarting the server?
I should add that the underlying problems seems to be WiFi related. The behavior is that the WiFi connection seems to break long enough that the shared volumes disconnects. Outlook also causes a break. This behavior seems to have started with 10.9 and the purchase of new Retina Display MacBook Pros. I turned off AppNap on the Office applications but that is not clearly helpful. I also have been told the problem seems more likely to occur when Word is open in the background and another program like Outlook is in the foreground.
Any suggestions appreciated.

Apple write an operating system and also produce file sharing software as part of that to be used as a file server. Apple provide documentation for third-party software developers on how they should write software to work with Apple's software and also give those developers early access to new versions so those third-party developers can test and if needed make adjustments and issue updates to cope with any Apple changes.
Some third-party developers are good at dealing with this, some are bad, and some totally ignore what Apple does and give the impression they don't care if their product works properly or not. I think we can all judge where Microsoft sits.
It appears Microsoft have never paid any attention in particular to how Apple expect file-locking to be handled when accessing files on a Mac server. There have been problems for years and years and years with Office. Two other problems I have seen which seem different to yours but probably related are -
With Office documents it is supposed to be possible for more than one person to edit the same file at the same time, consider it a miracle if this actually works
With Office in particular Word, there is an auto-save function, unfortunately the way this seems to be implemented it seems that Word creates a new temporary file each time it auto-saves the document and keeps all the previous temporary files open still, this eventually means potentially over a hundred temporary files are open - just for one Word document and you can then hit a limit on the total number of files you are allowed to have open at the same time. At this point further auto-saves fail, and you also encounter great difficulty doing a real full save of the document.
I do not hold Apple completely blameless over this issue, it is likely their file-locking implementations change too often, and have inadequate documentation, however even considering this a company the size of Microsoft with the amount of sales (and profit) they derive from Office for the Mac has no excuses at all for failing to put the effort in to resolve any such clearly critical problems.
We could go on and on about other areas where Microsoft don't play by the (software) rules. Even in Windows Office does not obey the standard print dialog rules Microsoft specified themselves!
Unfortunately not only is Office for Mac upgraded infrequently, but even when new paid for upgrades are released Microsoft have a history of still not fixing bugs. It goes without saying that a mere free update is even less likely to actually fix a bug, typically such free updates only address security issues. The next version of Office is going to be Office for Mac 2014 see http://www.macworld.com/article/2106643/microsoft-will-release-a-new-version-of- office-for-mac-this-year.html
One area I confidently predict Microsoft not to resolve in Office for Mac 2014 is that fact that Word for Mac still does not support right-to-left languages like Hebrew and Arabic. This is despite the fact that OS X itself has supported this for years and years, and despite the fact other Mac programs support this including the free TextEdit and Pages - both of which can read Word files. Some people may remember that at one point the Israeli Government temporarily banned all Microsoft software over this issue. See http://apple-beta.slashdot.org/story/03/10/15/2215249/israeli-government-suspend s-microsoft-contracts This issue goes back over TEN years!!
I note that Microsoft has now taken their OfficeForMac blog offline, probably due to the weight of criticisms. I would not say it is due to out-right anti-Microsoft hate, that war ended long ago. We just want products that work. I myself do use Microsoft products, even at home - where they are the best solution, so I use Microsoft Media Center for example. Sadly this is now being neglected by Microsoft.

Setting up an OSX Server as a Gateway between Wan and Lan

Hi there,
I just bought an OSX Server License and know im struggeling to setup my MacPro as a Gateway between my Lan and the Internet.
Im pretty new to these things I´m afraid, so a step-by-step list might help.....
I setup my en0 as PPPoE to my DSL-Modem what works fine.
Then i used the Gateway-Setup-Assistant to configure the DHCP,DNS Stuff....
Unfortunately none of the Clients in my Lan is able to connect to the Internet - the Server has got a connection but doesn´t pass it through somehow, although the Clients in my lan are connected to the Server.
Apple Resource and Help documentation is no help for me cause it just says use the Gateway Assistant and lean back.
I hope theres anyone out there understanding my issue and is willing to help!
Thanks a lot
Jan

Make sure you have the NAT service turned. If you can connect to the Internet from the server, but systems on the LAN can't get out, then NATting is the usual culprit! NAT (Network Address Translation) translates your WAN addresses to your LAN addresses. I've been through setting up OS X Server several times and usually end up doing it by hand instead of using the Assistant. I've seen problems in 10.4 server that when the DSL drops for a period of time for some reason NATting turns itself off. Don't know if Leopard server exhibits the same problem.
HTH.

Diffs b/n 10.4.3 clients and 10.3.9 on OSX Server 10.3.9

We have a smooth running OSX Server (standalone running 10.3.9) with mainly 10.3.9 clients (G3 iMacs to latest eMacs). When we configure brand new 10.4.3 clients (new eMacs) using the same settings in Directory Access we can't get login to work.
All that happens is that the Username and Password go grey and the machine hangs with frantic network activity (based on flickering lights on the switch). The dialog box doesn't shake.
In some cases the computer will eventually login but it takes several hours - usually though, not at all - or at least I get sick of waiting after a full school day.
Clearly there is some wrinkle about 10.4.3 that I can't see. If I clone one of our 10.3.9 machines onto the new machines they workl perfectly, but I want to use Tiger.
Everything is fully updated, network is 100baseT.
Steve Richards
Creswick PS
Australia
eMacs and a G4 Xserve Mac OS X (10.4.3) Server is 10.3.9

Stephen,
You seem to be doing pretty well for having trained yourself.
By forward and reverse lookups, I meant DNS lookups--I typically use nslookup, but lookupd will work too. If you get the server's IP address from the FQDN (foward lookup) and the FQDN from the IP address (reverse lookup), then your DNS settings are fine.
Ultimately, you should change the paths to your share points so they meet the requirements, but before you do that, I would run a test with a temporary share point to see if you can get your 10.4.3 clients to work. Use something like the default /Users share point--re-share it if necessary, and make sure you create a network mount record for it--and then set up a test user with its home directory in that share point. Then see if you can log in as that user on a 10.4.3 client.
If you still can't, try using the dscl command-line utility to see if you can see the directory records for your automount. Here's an example from our setup (what you type is in italics):
% dscl localhost
cd LDAPv3/10.1.0.101/Mounts
/LDAPv3/10.1.0.101/Mounts > ls
my.server.edu:/Volumes/Students
/LDAPv3/10.1.0.161/Mounts > read my.server.edu<tab to auto-complete>
cn: my.server.edu:/Volumes/Students
mountDirectory: /Network/Servers/
Basically, this tells you what mounts are published on your server. In your instance, you should see an entry for your Group Folders/Middle Years share point in the list from the ls command. If you can see the mount records for your home directory share points, and you can see the attributes of those records with the read command, that eliminates one possible source of the problem (whether the client is having problems binding to the server). This is unlikely to be the problem in your circumstances, but it's good to eliminate it out of the box.
Note that your server's entry may be listed by host name instead of IP address--in dscl, cd into the LDAPv3 directory and do an ls to see what's there. If you don't see an entry, or if you can't cd into the Mounts directory or you see nothing there, try rebuilding the Directory Access preferences from scratch. Log in as admin, delete the contents of /Library/Preferences/DirectoryService, reboot, and run Directory Access to re-add an LDAPv3 configuration for your server. When you do that, enter the server's IP address, and Directory Access should fill in the search base for you. Save, quit, and reboot the machine, and see if you can log in then.
Now, to your questions. Search base is in fact the dc=my,dc=com part. The ldapsearch command is useful if you need to see whether your client can bind to an LDAP server. It's actually not likely to be helpful in this situation, because your clients seem to be authenticating. I wasn't thinking when I added that suggestion. As to "static bind"--that just means that you are configuring Directory Access explicitly to contact a specific server, rather than letting the client get that information through DHCP.
If none of this helps, of course, post back. And good luck.
David Walton
Power Macintosh G5 1.8/PowerBook G4 15 1.42 Mac OS X (10.3.9)

DHCP provided address time limits

Hi there,
I have been searching for any way to limit DHCP supplied addresses in regards to time usage. I am looking to restrict certain addresses, specified via MAC, to only be able to access my network during specific times of the day.
For example, I would like for address 192.168.0.28 to only be able to access the network (and the internet of course) between the hours of 9 a.m. to 5 p.m.
If this cannot be done by OSX 10.5 Server, is there any affordable software or hardware solution out there that anyone knows of which can perform this function?

I removed the Belkin router and set up the Airport Time Capsule as the DHCP server. No problems since.

OSX-Server, iCal and Z10

Hello everybody,
i have a problem with syncing my iCal to my Z10 and I hope that there is a solution.
Im hosting my own OSX-Server 10.6 and on it there is the iCal-Servis witch runs perfectly with all Devices exept the Z10.
I inserted the login informations in the calendar setup and checked them multiple times but no succsess. In the Server logs there is only the massage that the login credentials aren´t correct. Is there a problem with the encryption of those?
I look forward to hear from you.
Many Thanks,
Neo7even

It's a known issue that the VPN client will not connect if it has a static address on the local network. You must get an address from DHCP. Maybe "DHCP with manual address" will work, but I don't know for sure.

OSX server + Private Network (and NAT) + Airport Extreme: Incompatibility ?

DHCP on Airport Extreme (AE) prevents some private network configuration.
*Imagine the following:*
- An AE that shares a public IP for your private network (NAT) => DHCPd is on (not an option)
- A Mac Mini with snow leopard and some services activated (Calendars, Wiki, Open Directory, ...) and a DNS with a private domain (e.g. you server is called: minisrv1.private)
- Client with account linked to an account on the OSX server
*Your problem:*
You can't activate a DHCP server on your OSX server: it will conflict with the one in your AE.
All your DHCP clients will get your AE address as DNS server and consequently wont be able to resolve any of your private addresses in your private domain
Your server will advertise all it's services with private domain's addresses
*==> All your client machines will get un-reachable services information (like iCal cannot connect to iCal server minisrv1.private)*
A solution might be to "trick" down the DHCP on the AE:
http://discussions.apple.com/thread.jspa?threadID=121990
Message was edited by: Philippe Rochat

I don't believe your analysis is correct.
You're right that when using the AirPort Extreme as an edge router connected to your ISP, and using NAT/DHCP to share its connect, the AE will configure all clients to use the AE as the DNS server (it actually acts as a DNS proxy).
However, it is still entirely possible to use your own, internal, private DNS server for those clients.
You see, the AE has its DNS server configuration in the Internet tab - this is where the AE will direct all DNS lookups, including those from DHCP clients.
Your solution is to just tell the AE to use your internal server for its DNS. That way it will be able to resolve your .private domain, and will enable all DHCP clients to do the same.

OSX Server DNS Setup

Hi Folks,
I am hoping someone out there can assist as its almost 2AM and I am still trying to get this thing working. I have a MacMini running OSX Server. I have 5 Mac Clients on my network and the purpose is basic file sharing, iCal, Address Book etc etc. I want to have a Local DNS service to resolve names on the LAN and have it forwarded to my ISP to resolve those its not authorative about.
I have configured the server to the point where it will:
- Resolve DNS queries from clients for addresses it is not authorative about by using the forward DNS servers.
- Resolve reverse queries eg: nslookup 192.168.1.100 (fixed ip for my srvmacmini)
But it will not resolve local hostnames, for example:
watsonad-mbpro:~ watsonad$ nslookup 192.168.1.100
Server: 192.168.1.100
Address: 192.168.1.100#53
100.1.168.192.in-addr.arpa name = srvmacmini.anthonywatson.net.au.
watsonad-mbpro:~ watsonad$ nslookup srvmacmini
Server: 192.168.1.100
Address: 192.168.1.100#53
** server can't find srvmacmini: NXDOMAIN
Looking into the logs which I have set into debug mode, I can see the following:
<truncated>/IN/com.apple.ServerAdmin.DNS.public: has no NS records
Now - I have tried recreating the zone entries, I can see them listed in /var/named/zones in the right db.* files and have walked through that configuration.
I have set the DNS entry for the server itself to 127.0.0.1 and numerous other suggestions I have seen in the posts here but just cannot seem to get this working.
Am hoping the guru's here can assist - ready and willing to trawl through logs etc if more info is needed. I can see others have had this problem but cannot seem to find the post where it got resolved in a way I could repeat the same steps.
Cheers

Looks like this ones not yet solved - I change the DHCP server from 127.0.0.1 to 192.168.1.100 and renewed the lease to refresh the settings:
watsonad-mbpro:~ watsonad$ hostname
watsonad-mbpro.anthonywatson.net.au
watsonad-mbpro:~ watsonad$ nslookup watsonad-mbpro
Server: 192.168.1.100
Address: 192.168.1.100#53
** server can't find watsonad-mbpro: NXDOMAIN
watsonad-mbpro:~ watsonad$ nslookup 192.168.1.16
Server: 192.168.1.100
Address: 192.168.1.100#53
16.1.168.192.in-addr.arpa name = watsonad-MBPro.anthonywatson.net.au.
watsonad-mbpro:~ watsonad$
So here are the zone entries, now these have all been created by server admin utility - below is the db.anthonywatson.et.au.zone.apple file , the one in the "named" directory points to this one of course:
;GUID=3B5D7974-F072-4F38-B319-76FCFB4CCF1E
;selfResolvingHostname=0
$TTL 10800
anthonywatson.net.au. IN SOA 127.0.0.1 Anthony.anthonywatson.net.au (
2011012912 ;Serial
86400 ;Refresh
3600 ;Retry
604800 ;Expire
345600 ;Negative caching TTL
anthonywatson.net.au IN NS 127.0.0.1
watsons-imac.anthonywatson.net.au IN A 192.168.1.51
watsons-imac.anthonywatson.net.au IN HINFO "iMac 27" "OSX Snow Leopard"
watsonad-MBPro.anthonywatson.net.au IN A 192.168.1.16
watsonad-MBPro.anthonywatson.net.au IN HINFO "Macbook Pro 13" "OSX 10.6 Snow Leopard"
srvmacmini.anthonywatson.net.au. IN A 192.168.1.100
srvmacmini.anthonywatson.net.au. IN HINFO "Mac Mini" "MAC OSX Server 10.6"
watsontm-MBPro.anthonywatson.net.au IN A 192.168.1.26
watsontm-MBPro.anthonywatson.net.au IN HINFO "13 Macbook Pro" "OSX Snow Leopard"
lb.dns-sd.udp IN PTR anthonywatson.net.au.
b.dns-sd.udp IN PTR anthonywatson.net.au.

OSX Server v4 - serveradmin --version == DEBUG

I am running latest and greatest on my MacPro3,1 server; serveradmin reports it no version # (DEBUG)
I have been experiencing issues since upgrading; I found that the /usr/sbin/post* commands differ from the versions in /Applications/Server.app/.../usr/sbin
Moved originals to .orig for /usr/sbin/post* and linked to /Applications.../usr/sbin/post*
Moved original /etc/postfix to .orig and linked to /Library/Server/Mail/Config/postfix
Not a very clean install; should either eliminate postfix from standard install or remove when installing Server (or use existing and not bring own copy of postfix).

Looks like this ones not yet solved - I change the DHCP server from 127.0.0.1 to 192.168.1.100 and renewed the lease to refresh the settings:
watsonad-mbpro:~ watsonad$ hostname
watsonad-mbpro.anthonywatson.net.au
watsonad-mbpro:~ watsonad$ nslookup watsonad-mbpro
Server: 192.168.1.100
Address: 192.168.1.100#53
** server can't find watsonad-mbpro: NXDOMAIN
watsonad-mbpro:~ watsonad$ nslookup 192.168.1.16
Server: 192.168.1.100
Address: 192.168.1.100#53
16.1.168.192.in-addr.arpa name = watsonad-MBPro.anthonywatson.net.au.
watsonad-mbpro:~ watsonad$
So here are the zone entries, now these have all been created by server admin utility - below is the db.anthonywatson.et.au.zone.apple file , the one in the "named" directory points to this one of course:
;GUID=3B5D7974-F072-4F38-B319-76FCFB4CCF1E
;selfResolvingHostname=0
$TTL 10800
anthonywatson.net.au. IN SOA 127.0.0.1 Anthony.anthonywatson.net.au (
2011012912 ;Serial
86400 ;Refresh
3600 ;Retry
604800 ;Expire
345600 ;Negative caching TTL
anthonywatson.net.au IN NS 127.0.0.1
watsons-imac.anthonywatson.net.au IN A 192.168.1.51
watsons-imac.anthonywatson.net.au IN HINFO "iMac 27" "OSX Snow Leopard"
watsonad-MBPro.anthonywatson.net.au IN A 192.168.1.16
watsonad-MBPro.anthonywatson.net.au IN HINFO "Macbook Pro 13" "OSX 10.6 Snow Leopard"
srvmacmini.anthonywatson.net.au. IN A 192.168.1.100
srvmacmini.anthonywatson.net.au. IN HINFO "Mac Mini" "MAC OSX Server 10.6"
watsontm-MBPro.anthonywatson.net.au IN A 192.168.1.26
watsontm-MBPro.anthonywatson.net.au IN HINFO "13 Macbook Pro" "OSX Snow Leopard"
lb.dns-sd.udp IN PTR anthonywatson.net.au.
b.dns-sd.udp IN PTR anthonywatson.net.au.

Apache virtual host with OSX Server?

I have been running OSX Server for a while now, and just recently I decided to get McMyAdmin for my Minecraft server. The web client for McMyAdmin runs on port 8080, but I wanted it on port 80. I wanted to use it with my domain, so I just created a sub domain and pointed it to my server. The problem is that OSX Server apparently doesn't let me use port 80, even when websites are turned off. I decided to delete Server and just use plain apache. This worked until I realized that my website was only accessible locally. I have all the correct ports forwarded, etc. But I get the error:
Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.
when I try to connect from outside my network. This is probably just some simple thing I missed but it would be nice if someone could just point out what I did wrong here. Back to the point, I want to know how to run the proxy to my web client on port 8080 AND ALSO run OSX Server with or without apache virtualhost.
Thanks in advance,
Eamon

Web is stupidly easy - Apache has extensive support for multiple virtual hosts in a single server and will happily support as many domains/hostnames as you can throw at it.
Mail is a little trickier since it needs to hook into some kind of directory server to validate user addresses.
Mac OS X's Open Directory does support this, but it's a little cumbersome (basically every user has to exist in the main Open Directory domain as well as having a secondary email address(es) in the other domain(s).
This can get especially tricky when you have users with the same shortname in different domains - for example if you give [email protected] a secondary email address of [email protected] and you then get a new user [email protected], you can't give the third 'joe' the address 'joe' in Open Directory since that's already taken. This means he'll have to login using different credentials from his email address. Confused yet? You bet.
If you're prepared to eschew Open Directory you can just use Postfix's built-in support for virtual hosting, but it's a little more complex to setup and support and is entirely command-line based (i.e. there's no GUI for setting it up or supporting it).
So, for that reason you might be prepared to setup multiple virtual machines for each domain. It really depends on how much the domains are related (if at all).

Help with OSX server mail setup

Please if anyone can tell me what I am doing wrong, I would be very grateful. I have a company with an externaly hosted website and an an internally hosted email (OSX server). I have everything kind of working, but some things don't seem quite right. I'll explain below:
I have a purchased domain: mycompany.com hosted by godaddy.
I am using Godaddy name servers: ns65.domaincontrol.com and ns66.domaincontrol.com
The external godaddy DNS has an a name entry for my mail server: mail pointing to 123.123.123.123 (which is my companies external static IP address).
There is also a null (@) a name record for my website hosting service (squarespace) pointing to 456.456.456.456
There is a cName record www pointing to the squarespace domain "www.squarespace6.com" (know this is unusual, but it is how squarespace asks this to be set up and does not work otherwise)
There is an MX record with priority 10 and host name @ pointing to mail.mycompany.com
I have a airport extreme router with the appropriate ports forwarded to the OSX server.
The DNS servers on the router are pointed to the internal IP address of the OSX server
I did not change the domain name on the router (mistake?) it is currently san.rr.com
On the OSX server I have set up host name to be mycompany.comDNS is set up with primary zone being mycompany.com
Primary Zone entries include
nameserver = mycompany.com
machine record host name is mycompany.com and the IP address is the internal IP address of the OSX server
another machine record with host name "mail" and IP address is the internal IP address of the OSX server.
Finally, there is a mail exchanger record with mail server "mail.mycompany.com" and priority 10
There are 2 entries autocreated in the Reverse zone
Mail is setup and running on the OSX server providing mail for "mail.mycompany.com"
Users are setup with email address: [email protected] (note: without the mail subdomain - I think this is OK?)
I am using self signed certificate.
In my clients (windows Thunderbird, Mac Mail, iOS mail), the settings are for the incoming mail server host name to be "mail.mycompany.com" and the outgoing also to be "mail.mycompany.com"
I woud have expected this to be imap.mycompany.com and smtp.mycompany.com respectively, but it doesn't work when I input these values and works with the former. Have I set this up wrong?? imap seems to require SSL on port 993 and SMTP seems to require TLS on port 587.Outlook on PC gives me an error that after googling appears to be a problem with not recognizing a fuly qualified hostname form the SMTP client. I see the fix, but wanted to know if that meant that my server didn't have a fully qualified host name and whether I should change that rather than just remove that restriction???
The final problem is that my outgoing emails seem to be getting caught up in other people's spam filters too frequently. What is the main reason for this? Is it because I have set something up wrong and it brings up flags or is it simply because I am not a huge hosting company, or somethign else althogether?
If you've gotten this far, big thanks! If you can help me, even more thanks!

Well, actually they are both getting caught up in spam filters and bounced back. I actually realized that part of the problem is that I have a dynamic IP address, but it doesn't change. Regardless, on the bounce back it looks like hotmail and other domains are rejecting email from my IP and recognize it as dynamic. This was a test server that i would by physically taking to my business where there is a static business IP address (Cox).
Sorry for the very long original message, but it seems that most people don't post enough information for the problem to be solved in their original posts and I was hoping to provide as much detail as possible.
The other is the question of "are things set up right?" It seems strange to me that both my outgoing and incoming servers are "mail.mycompany.com" and not imap.mycompany.com and smtp.mycompany.com and I wonder if this is going to cause me to have problems?
Is it a problem that my email addresses are [email protected] and not [email protected]?
Was I supposed to change the domain name on the router?
Also is it going to be a problem that I am using a self signed certificate?

Cant connect to OSX server over network in recovery mode

Hi guys.
First of all, thanks for any help you can give me.
I am running osx server on a mavericks mac mini on a home network. Attached to it I have a 1tb hard drive to which all the macs in my house use time machine to back up over my network and they are stored there.
I have just formatted one of my macs and want to restore it from these time machine backups that are on the osx server on my network.
When i enter recovery mode from boot (COMMAND R), it can see the "backups" on networks "Matts-Mac-Mini" but when i then click "CONNECT" it says "Enter your name and password for the server "Matts-Mac-Mini/local" so that Time Machine can access it.
It gives me a box with NAME and PASSWORD and a CONNECT button.
By DEFAULT the "NAME" it starts with is "root".......which I dont understand.
I have tried every single iteration of names and passwords I can think of but it still wont connect, it either shakes the box or gives an error saying "There was a problem connecting to the server "Matts-Mac-mini.local". Check the server name of IP address and then try again".
I have tried the log in details for the osx server, the login details for the mac im trying to connect from, used root as the username, tried capitals, no capitals, spaces no spaces etc. I am at a total loss and about to tear my hair out!!
Is there anyone able to give me any help with this please, I would be SO grateful!
Many thanks,
hardtofin

I think I have isolated the password, with a certain username and password the box never shakes and instead gives the error: "There was a problem connecting to the server "Matts-Mac-mini.local". Check the server name of IP address and then try again".
Are you able to offer any help with this? I dont see why i can't connect to it, if the imac can already see it?
Many thanks again,
hardtofin

Releasing unused DHCP IP addresses in OSX Server 10.4

Similar Messages

Maybe you are looking for