What is my iMacs network domain or name?

I am trying to connect to a PC through a router. I read somewhere that the PC and iMac have to have the same domain name. The PC domain name is "WORKGROUP". I seem to remember seeing the iMac's domain name when I was setting up the computer, but I can't find it now. Does anyone know how to find this information?

Don't do this. At least not without a lot of thought.
You're talking of taking your PC and hanging its proverbial a** out in the wild. You're just asking for hackers to take over your machine. It's easy enough to take over a PC that's properly firewalled, let alone one that has public services running.
You would be better off implementing a VPN - at least then you'll connect securely to your home/office network and you're at no more risk than you would be if you were sitting on the same LAN.

Similar Messages

  • What does this mean?  This computer's local hostname "Linda-Daviss-iMac-4.local" is already in use on this network. The name has been changed to "Linda-Daviss-iMac-5.local".

    What does this mean: This computer’s local hostname “Linda-Daviss-iMac-4.local” is already in use on this network. The name has been changed to “Linda-Daviss-iMac-5.local”.
    When I came back to my computer this message was on the screen.  Should I be concerned ? or doing something?

    Sometimes this message means that you have two simultaneous connections to the same local network: probably Ethernet and Wi-Fi. Disconnect the Ethernet cable or turn off Wi-Fi.
    Sometimes it happens because a device that gets its network address from the router wakes from sleep, and the address it was using before has been assigned to another device.
    Rename the computer in the Sharing preference pane.

  • HT5167 Error after 10.7.4 upgrade..."computer's local hostname ........is already in use on this network.  The name has been changed to......  What to do now to get it back to status before 10.7.4 upgrade?

    Error after 10.7.4 Lion Upgrade to iMac
    Computer's local host name .......is already in use on this network.  the name has been changed to........
    and it keeps adding up the number each time I wake the iMac.
    What to do to get it back before upgrade error?

    Ok worth repeating, hope this works.  Finally spoke to AppleCare Support and walked me thru following...restart computer holding down "command" and "option" keys at the same time with letters "P" and "R" when computer turns on.  This is what he called a PR restart, clears out discrepancies in memory (if that is what the error message actually is).  Then went to Systems Preferences/Network/Sharing and deleted the number that kept increasing every time MAC would wake up.
    Even tho this was just done, I am hopeful that error pop-up won't happen again.  Fingers crossed!

  • How to get localcomputer network  domain name?

    HI all
       Does any one know how to get  localcomputer's network domain name !  I call use function to get  local computername in sap system! But I could not find any functions to get network domain !

    Below link may be useful, check reply from Poornanand.
    Get user system domain name ?

  • What API i can see network card driver name

    Dear all
    in java i/o evirnment what API I can use to call current machine network card driver name?

    Well the first step for you is to look through your Windows documentation to see what the library call is to get the information you want. Can you find that and post what you find, and post the full signature of that library call (ie, arguments and return type)?
    In other words, here's what you should do: Write a simple C program that gets just the information you are looking for. How that works is outside the scope of JNI, so it's outside the scope of this forum, but once you get that working, post some info about it and I'll explain how to get that linked in with JNI. The good news is, it's easy to do.

  • I get this message:This computer's local hostname "x-8.local" is already in use on this network. The name has been changed to "x-9.local" I have turned off sharing and it continues to upgrade name. What is the fix?

    I get this message: This computer’s local hostname “x-8.local” is already in use on this network. The name has been changed to “x-9.local” I have turned off sharing and it continues to upgrade name. What is the fix?

    Hi, this is a common problem, mostly just irksome though.
    It can have many cause, like using more than one Interface for connections, Router temporarily losing x.local & seeing a new connection with x.local already used, insists it must be x-1.local, x-2.local, etc..
    What all Sharing do you have enabled?
    Some possible fixes...
    http://forums.macrumors.com/showthread.php?t=542899
    https://discussions.apple.com/thread/3941367

  • What's wrong with networking since Leopard?

    Hi,
    I'm with Mac since years. I was a PC User once and spent hours with all kinds of network troubles. What convinced me with Mac right in the beginning was easy networking: It just worked!
    But since Leopard things got worse: I have several MBP's, iMacs, Airport Extreme's and Airport Express's at different places which I installed, and I face the same problems at EVERY place:
    - I can't connect to AExtreme for several reasons: timeout, security incompatibility, ...
    - Sometimes only two Macs are allowed to connect to one AExtreme
    - Airport doesn't find Aiport or any other networks for minutes
    - After connecting to the router, can't get an IP (self-assigned IP only) - other PCs get an IP.
    - Aiport Extreme crashes (yellow blinking)
    - connection loss (even when AExtreme is very close)
    Now I know about networking, about configuration, I've done this for years. Whatever I do, problems disappear and appear again, at different times, at different places with different hardware.
    What is wrong with Leopard? Such problems remind me of times with Windows98 and stuff like that.

    What's wrong with networking since Leopard?
    on my network and many i have setup there have been no problems with leopard. However there are always teething problems with new operating systems. Thankfully with leopard only a tiny percentage of users experience technical difficulties.
    can't connect to AExtreme for several reasons: timeout, security incompatibility,
    is it set to use WPA/WPA2
    Airport doesn't find Aiport or any other networks for minutes
    sometimes my macbook pro takes a while to show up any networks if there are lots in the area this is because it is scanning them all.
    After connecting to the router, can't get an IP (self-assigned IP only) - other PCs get an IP.
    What kind of router are you using? What happens if you powercycle the router?
    # Aiport Extreme crashes (yellow blinking)
    # connection loss (even when AExtreme is very close)
    Have you tried resetting your AE to default. reinstalling its firmware or checking for a firmware update?
    Have you tried changing hte wireless channel your networ is broadcasting on?
    What is wrong with Leopard? Such problems remind me of times with Windows98 and stuff like that.
    Did you upgrade install your leopard installation or did you do clean (erase) installations?
    Have you tried created new network locations?

  • Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."

    Hi,
    Windows 7 or Windows Server 2008 R2 domain join displays error "Changing the Primary Domain DNS name of this computer to "" failed...."
    DC:windows Server 2008 R2
    Domain functional level:Windows Server 2003
    When Winxp join domain, have no this error message.
    I checked http://support.microsoft.com/kb/2018583?wa=wsignin1.0 does't work.
    There have 3 suggestion in this article:
    1.The "Disable NetBIOS over TCP/IP" checkbox has been disabled in the IPv4 properties of the computer being joined.
    Doesnt's work.
    2.Connectivity over UDP port 137 is blocked between client and the helper DC servicing the join operation in the target domain.
    On my DC, I run netstat -an, reslut as below:
     UDP    192.168.20.3:137       *:*
    3.The TCP/IPv4 protocol has been disabled so that the client being joined or the DC in the destination domain targeted by the LDAP BIND is running TCP/IPv6 only.
    We are not using IPV6.
    This server recently updated from Windows Server 2003 to Windows Server 2008 R2. Before upgrade, when Win7 and Win2008 join this domain, also have the same error message.
    Please help to check this issue.
    Thank you very much.
    BR
    Guo YingHui 

    Hi Guo Ying,
    I have faced this critical error which makes over-writes the host names in the domain when you join.
    For example: Already you had a host name called as PC.domain.com in the domain.com Domain.
    When you try to add the another host name called as PC in the domain.com Domain, it doesn't give you the duplicate name error on the network it does over-write the existing host name called as PC.domain.com & it will add the new host name into the domain.
    Host name which got over-written will get removed from the domain. I faced this issue in my project. My DPM host name got removed from the Domain & new host name got joined into the domain which halted my backups for one day.
    Final Resolution is as follows:
    You need to start the dns console on the DC & drop down the domain name.
    Select the _msdcs when you click on _msdcs it will show the Name Server's list on the right hand side.
    You need to add the Domain Naming Master under the _msdcs or add all the domain controllers which you had.
    After you add the Name server's try joining the PC OR Laptop to the domain which is successfully joins it.
    Regards
    Anand S
    Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

  • I can't connect to other computers on my network with computer names. Any suggestions?

    i can't connect to other computers on my network with computer names. Any suggestions?

    In what way are you trying to connect? File sharing? Printer sharing? Screen sharing? Something else?
    How are your computers connected to this network? What happens when you try to connect to them?
    Best of luck.

  • Cannot see NAS on my local network by its name (Linksys EA4500)

    Hello,
    I have just bought a new EA4500 and set it up at home. Most things worked like a charm except one. I can no longer see my Synology NAS on my home network byt its name.
    I have the router connected to internet (local ISP, PPPoE). I have the NAS connected by wire, two Windows 8 PCs connected wirelessly. There is also a TV (wired connection), a printer, some Windows Phones and Kindles. One of the PC cannot see the NAS (the other can). It can connect to it by its IP (in browser, by ping), it can see its media server (I can play music from the NAS in my Media Player), the TV sees the NAS as DLNA media server... But the PC cannot see the NAS by its name.
    If I list connected devices on the router settings, I can see the NAS and its name. But the PC cannot. What is wrong?
    Both PCs have file sharing turned on. I have even SSH'd to the NAS ind successfully pinged the PC by its name. For full disclosure, the PC has VMWare installed with Windows 7 virtual machine.
    I made no settings to the router other than going through the Cisco Connect wizard and disabling guest wifi.
    Thank you very much for any suggestions.
    Solved!
    Go to Solution.

    Thank you. Restarting everything didn't help. It happed to be solved by itself later on. I was fiddling with wifi settings and set (and unset) FIPS. Then it worked. No idea if it was a coincidence.

  • I recently got a message on my screen that says "the name of your computer is already in use on this network. The name has been changed to *

    I recently got a message with an exclamation mark stating "your computer name is already in use on this network. The name has been changed to ______"
    How did this happen, is it phishing, malware, or did someone hit some button on here to change it. I'm hoping that someone else doesn't have access to everything on my computer now. Help!

    Hello RaptorTrish,
    Interesting name!   You don't say what computer you are using, the OS or the nature of the network, home, office etc.    Could you fill in a few details.  
    You are right to be concerned but there is often a simple explanation.

  • Should I ok "this computer's local hostname Irma-Mac-mini-local" is already in use on this network. The name has been changed to Irma2 Mac-mini 2-local

    Should I ok this message-this computer's local hostname Irma's Mac-mini-local is already in use on this network. The name has been changed to Irma's Mac-mini-2local

    Don't think this is a conflict with IP Addresses or computer names
    = DHCP hangover when computer renews DHCP lease
    There is no actual other computer
    It just appears that way when reconnects so creates new -2 computer name
    What types of names do you use your computers ?
    Whether you name them after quantum particles or the romantic poets...
    They will each start to be appended with "-2" then "-3" etc if you auto configure network settings from Airport Router  DHCP service and you have this Change computer name issue where pop up window states name is already being used on your LAN
    As stated previous post you can reset the computer name in SysPrefs / Sharing / Edit button
    And restart Router or renew all DHCP leases (if persists in not allowing original name)
    Can now press Edit and reset name of choice
    But for Fix see link above

  • Cannot DNS resolve across networks using host name only (not fqdn)

    Evening all,
     I currently run domain network (MS Server 08 - dhcp) on my firewall interface1 and WiFi network on interface2 (dhcp provided by router itself). On my Wifi dhcp I am advertising as DNS server that of the domain, but wifi clients can resolve only FQDN domain
    client names not host names ("domainclient.domain.local" - not "domainclient").
    If on my wifi client I change NIC properties -> IPV4->Advance->DNS-> append these suffixes, and put the domain.local, then it works but need to be able to work without manual changes to each client.
    Any ideas?
    Many thanks,
    Argyris

    Hi,
    Additional, please confirm your DHCP option have configure the correct WINS server.
    The related KB:
    Understanding DNS Client Settings
    http://technet.microsoft.com/en-us/library/cc754152.aspx
    Configuring TCP/IP networking
    http://msdn.microsoft.com/en-us/library/dd163570.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • IMac Network Adapter Slowed Recently

    Hi guys,
    I've recently noticed that my iMac network adapters (ethernet and wireless) have slowed down considerably recently. I'm trying to troubleshoot and I'm hoping that someone here will be able to help.
    System:
    iMac (Mid 2011)
    3.1Ghz i5
    12GB 1333Mhz DDR3
    OS X 10.8.1 (12B19)
    Ethernet:
    Media Options: Full Duplex, Flow Control
    Media Subtype: 1000baseT
    My broadband is capable of 20Mbps down, 1Mbps up.
    Here's the Speedtest result on ethernet:
    It'll start up fast (around 7-8Mbps, but gradually get slower throughout the speed test. Results are similar on Wifi.
    Here's the Speedtest result of a Mac Mini located just beside the iMac but performed via Wifi on the same router.
    In a file transfer test to the Mac Mini via Gigabit ethernet, it can only achieve 7MB/s.
    Any ideas anyone?

    Hi Linc,
    The info tab revealed 0 sent and received errors and 0 collissions on both the iMac and Mac Mini. (Note that the Mac Mini is running Lion)
    Netstat results indicate that a lot more data packets from the iMac had to be retransmitted:
    iMac netstat results:
    tcp:
              12725851 packets sent
                        7378339 data packets (3578581558 bytes)
                        77047 data packets (85466861 bytes) retransmitted
                        0 resends initiated by MTU discovery
                        5045141 ack-only packets (26360 delayed)
                        0 URG only packets
                        23 window probe packets
                        146918 window update packets
                        79000 control packets
                        1026 data packets sent after flow control
              11975975 packets received
                        4083169 acks (for 3578629498 bytes)
                        442821 duplicate acks
                        0 acks for unsent data
                        7346301 packets (2001710181 bytes) received in-sequence
                        7741 completely duplicate packets (5592579 bytes)
                        13 old duplicate packets
                        23 packets with some dup. data (1453 bytes duped)
                        486714 out-of-order packets (430717886 bytes)
                        0 packets (0 bytes) of data after window
                        0 window probes
                        5454 window update packets
                        2930 packets received after close
                        3 bad resets
                        0 discarded for bad checksums
                        0 discarded for bad header offset fields
                        0 discarded because packet too short
              40964 connection requests
              64 connection accepts
              0 bad connection attempts
              0 listen queue overflows
              39675 connections established (including accepts)
              46504 connections closed (including 1921 drops)
                        2710 connections updated cached RTT on close
                        2710 connections updated cached RTT variance on close
                        558 connections updated cached ssthresh on close
              710 embryonic connections dropped
              2628367 segments updated rtt (of 2612162 attempts)
              31280 retransmit timeouts
                        79 connections dropped by rexmit timeout
                        0 connections dropped after retransmitting FIN
              52 persist timeouts
                        0 connections dropped by persist timeout
              689 keepalive timeouts
                        2 keepalive probes sent
                        514 connections dropped by keepalive
              2070030 correct ACK header predictions
              6663985 correct data packet header predictions
              37075 SACK recovery episodes
              64828 segment rexmits in SACK recovery episodes
              77072533 byte rexmits in SACK recovery episodes
              467418 SACK options (SACK blocks) received
              257920 SACK options (SACK blocks) sent
              0 SACK scoreboard overflow
    udp:
              124653 datagrams received
              0 with incomplete header
              0 with bad data length field
              0 with bad checksum
              1156 dropped due to no socket
              70045 broadcast/multicast datagrams dropped due to no socket
              25724 dropped due to full socket buffers
              0 not for hashed pcb
              27728 delivered
              113693 datagrams output
    ip:
              12102114 total packets received
              0 bad header checksums
              0 with size smaller than minimum
              0 with data size < data length
              0 with ip length > max ip packet size
              0 with header length < data size
              0 with data length < header length
              0 with bad options
              0 with incorrect version number
              0 fragments received
              0 fragments dropped (dup or out of space)
              0 fragments dropped after timeout
              0 packets reassembled ok
              12097702 packets for this host
              2047 packets for unknown/unsupported protocol
              0 packets forwarded (0 packets fast forwarded)
              279 packets not forwardable
              2086 packets received for unknown multicast group
              0 redirects sent
              12905846 packets sent from this host
              0 packets sent with fabricated ip header
              0 output packets dropped due to no bufs, etc.
              348 output packets discarded due to no route
              0 output datagrams fragmented
              0 fragments created
              0 datagrams that can't be fragmented
              0 tunneling packets that can't find gif
              3 datagrams with bad address in header
              0 packets dropped due to no bufs for control data
    icmp:
              1151 calls to icmp_error
              0 errors not generated 'cuz old message was icmp
              Output histogram:
                        destination unreachable: 1151
              0 messages with bad code fields
              0 messages < minimum length
              0 bad checksums
              0 messages with bad length
              0 multicast echo requests ignored
              0 multicast timestamp requests ignored
              Input histogram:
                        destination unreachable: 388
              0 message responses generated
              ICMP address mask responses are disabled
    igmp:
              1888 messages received
              0 messages received with too few bytes
              0 messages received with wrong TTL
              0 messages received with bad checksum
              0 V1/V2 membership queries received
              951 V3 membership queries received
              0 membership queries received with invalid field(s)
              938 general queries received
              13 group queries received
              0 group-source queries received
              0 group-source queries dropped
              937 membership reports received
              0 membership reports received with invalid field(s)
              937 membership reports received for groups to which we belong
              0 V3 reports received without Router Alert
              315 membership reports sent
    ipsec:
              0 inbound packets processed successfully
              0 inbound packets violated process security policy
              0 inbound packets with no SA available
              0 invalid inbound packets
              0 inbound packets failed due to insufficient memory
              0 inbound packets failed getting SPI
              0 inbound packets failed on AH replay check
              0 inbound packets failed on ESP replay check
              0 inbound packets considered authentic
              0 inbound packets failed on authentication
              0 outbound packets processed successfully
              0 outbound packets violated process security policy
              0 outbound packets with no SA available
              0 invalid outbound packets
              0 outbound packets failed due to insufficient memory
              0 outbound packets with no route
    ip6:
              3227 total packets received
              0 with size smaller than minimum
              0 with data size < data length
              0 with bad options
              0 with incorrect version number
              0 fragments received
              0 fragments dropped (dup or out of space)
              0 fragments dropped after timeout
              0 fragments that exceeded limit
              0 packets reassembled ok
              3162 packets for this host
              0 packets forwarded
              0 packets not forwardable
              0 redirects sent
              1583 packets sent from this host
              0 packets sent with fabricated ip header
              0 output packets dropped due to no bufs, etc.
              3 output packets discarded due to no route
              111 output datagrams fragmented
              224 fragments created
              0 datagrams that can't be fragmented
              0 packets that violated scope rules
              0 multicast packets which we don't join
              Input histogram:
                        TCP: 311
                        UDP: 2851
                        ICMP6: 63
              Mbuf statistics:
                        358 one mbuf
                        two or more mbuf:
                                  lo0= 969
                        1900 one ext mbuf
                        0 two or more ext mbuf
              0 packets whose headers are not continuous
              0 tunneling packets that can't find gif
              0 packets discarded due to too may headers
              0 failures of source address selection
              0 forward cache hit
              0 forward cache miss
              0 packets dropped due to no bufs for control data
    icmp6:
              5 calls to icmp_error
              0 errors not generated because old message was icmp error or so
              0 errors not generated because rate limitation
              Output histogram:
                        unreach: 5
                        router solicitation: 54
                        neighbor solicitation: 42
                        neighbor advertisement: 41
                        MLDv2 listener report: 51
              0 messages with bad code fields
              0 messages < minimum length
              0 bad checksums
              0 messages with bad length
              Input histogram:
                        neighbor solicitation: 24
                        neighbor advertisement: 39
              Histogram of error messages to be generated:
                        0 no route
                        0 administratively prohibited
                        0 beyond scope
                        0 address unreachable
                        5 port unreachable
                        0 packet too big
                        0 time exceed transit
                        0 time exceed reassembly
                        0 erroneous header field
                        0 unrecognized next header
                        0 unrecognized option
                        0 redirect
                        0 unknown
              0 message responses generated
              0 messages with too many ND options
              0 messages with bad ND options
              0 bad neighbor solicitation messages
              0 bad neighbor advertisement messages
              0 bad router solicitation messages
              0 bad router advertisement messages
              0 bad redirect messages
              0 path MTU changes
    ipsec6:
              0 inbound packets processed successfully
              0 inbound packets violated process security policy
              0 inbound packets with no SA available
              0 invalid inbound packets
              0 inbound packets failed due to insufficient memory
              0 inbound packets failed getting SPI
              0 inbound packets failed on AH replay check
              0 inbound packets failed on ESP replay check
              0 inbound packets considered authentic
              0 inbound packets failed on authentication
              0 outbound packets processed successfully
              0 outbound packets violated process security policy
              0 outbound packets with no SA available
              0 invalid outbound packets
              0 outbound packets failed due to insufficient memory
              0 outbound packets with no route
    rip6:
              0 messages received
              0 checksum calcurations on inbound
              0 messages with bad checksum
              0 messages dropped due to no socket
              0 multicast messages dropped due to no socket
              0 messages dropped due to full socket buffers
              0 delivered
              0 datagrams output
    pfkey:
              12 requests sent to userland
              1232 bytes sent to userland
              histogram by message type:
                        register: 3
                        x_spdadd: 4
                        x_spddelete: 4
                        x_spddump: 1
              0 messages with invalid length field
              0 messages with invalid version field
              0 messages with invalid message type field
              0 messages too short
              0 messages with memory allocation failure
              0 messages with duplicate extension
              0 messages with invalid extension type
              0 messages with invalid sa type
              0 messages with invalid address extension
              15 requests sent from userland
              2016 bytes sent from userland
              histogram by message type:
                        register: 3
                        x_spdadd: 4
                        x_spddelete: 4
                        x_spddump: 4
              0 messages toward single socket
              0 messages toward all sockets
              0 messages toward registered sockets
              0 messages with memory allocation failure
    Mac Mini netstat results:
    tcp:
              1228722 packets sent
                        531397 data packets (232421306 bytes)
                        1804 data packets (4683389 bytes) retransmitted
                        0 resends initiated by MTU discovery
                        333125 ack-only packets (397 delayed)
                        0 URG only packets
                        0 window probe packets
                        357458 window update packets
                        5280 control packets
              2894121 packets received
                        538797 acks (for 232379698 bytes)
                        4722 duplicate acks
                        0 acks for unsent data
                        2323757 packets (3221388063 bytes) received in-sequence
                        410 completely duplicate packets (141674 bytes)
                        6 old duplicate packets
                        1 packet with some dup. data (22 bytes duped)
                        37937 out-of-order packets (33733100 bytes)
                        0 packets (0 bytes) of data after window
                        0 window probes
                        349 window update packets
                        284 packets received after close
                        0 bad resets
                        0 discarded for bad checksums
                        0 discarded for bad header offset fields
                        0 discarded because packet too short
              2854 connection requests
              168 connection accepts
              6 bad connection attempts
              0 listen queue overflows
              2512 connections established (including accepts)
              3574 connections closed (including 84 drops)
                        68 connections updated cached RTT on close
                        68 connections updated cached RTT variance on close
                        40 connections updated cached ssthresh on close
              458 embryonic connections dropped
              537634 segments updated rtt (of 491250 attempts)
              4106 retransmit timeouts
                        0 connections dropped by rexmit timeout
                        0 connections dropped after retransmitting FIN
              0 persist timeouts
                        0 connections dropped by persist timeout
              302 keepalive timeouts
                        0 keepalive probes sent
                        284 connections dropped by keepalive
              58699 correct ACK header predictions
              1682300 correct data packet header predictions
              429 SACK recovery episodes
              511 segment rexmits in SACK recovery episodes
              402294 byte rexmits in SACK recovery episodes
              2890 SACK options (SACK blocks) received
              22021 SACK options (SACK blocks) sent
              0 SACK scoreboard overflow
    udp:
              35939 datagrams received
              0 with incomplete header
              0 with bad data length field
              0 with bad checksum
              166 dropped due to no socket
              25259 broadcast/multicast datagrams dropped due to no socket
              1 dropped due to full socket buffers
              0 not for hashed pcb
              10513 delivered
              3917 datagrams output
    ip:
              2929021 total packets received
              0 bad header checksums
              0 with size smaller than minimum
              0 with data size < data length
              0 with ip length > max ip packet size
              0 with header length < data size
              0 with data length < header length
              0 with bad options
              0 with incorrect version number
              0 fragments received
              0 fragments dropped (dup or out of space)
              0 fragments dropped after timeout
              0 packets reassembled ok
              2927160 packets for this host
              1861 packets for unknown/unsupported protocol
              0 packets forwarded (0 packets fast forwarded)
              0 packets not forwardable
              0 packets received for unknown multicast group
              0 redirects sent
              1234179 packets sent from this host
              0 packets sent with fabricated ip header
              0 output packets dropped due to no bufs, etc.
              1 output packet discarded due to no route
              0 output datagrams fragmented
              0 fragments created
              0 datagrams that can't be fragmented
              0 tunneling packets that can't find gif
              0 datagrams with bad address in header
              0 packets dropped due to no bufs for control data
    icmp:
              166 calls to icmp_error
              0 errors not generated 'cuz old message was icmp
              Output histogram:
                        destination unreachable: 166
              0 messages with bad code fields
              0 messages < minimum length
              0 bad checksums
              0 messages with bad length
              0 multicast echo requests ignored
              0 multicast timestamp requests ignored
              Input histogram:
                        destination unreachable: 29
              0 message responses generated
              ICMP address mask responses are disabled
    igmp:
              1832 messages received
              0 messages received with too few bytes
              0 messages received with wrong TTL
              0 messages received with bad checksum
              0 V1/V2 membership queries received
              916 V3 membership queries received
              0 membership queries received with invalid field(s)
              916 general queries received
              0 group queries received
              0 group-source queries received
              0 group-source queries dropped
              916 membership reports received
              0 membership reports received with invalid field(s)
              916 membership reports received for groups to which we belong
              0 V3 reports received without Router Alert
              930 membership reports sent
    ipsec:
              0 inbound packets processed successfully
              0 inbound packets violated process security policy
              0 inbound packets with no SA available
              0 invalid inbound packets
              0 inbound packets failed due to insufficient memory
              0 inbound packets failed getting SPI
              0 inbound packets failed on AH replay check
              0 inbound packets failed on ESP replay check
              0 inbound packets considered authentic
              0 inbound packets failed on authentication
              0 outbound packets processed successfully
              0 outbound packets violated process security policy
              0 outbound packets with no SA available
              0 invalid outbound packets
              0 outbound packets failed due to insufficient memory
              0 outbound packets with no route
    ip6:
              3204 total packets received
              0 with size smaller than minimum
              0 with data size < data length
              0 with bad options
              0 with incorrect version number
              138 fragments received
              0 fragments dropped (dup or out of space)
              0 fragments dropped after timeout
              0 fragments that exceeded limit
              69 packets reassembled ok
              3161 packets for this host
              0 packets forwarded
              0 packets not forwardable
              0 redirects sent
              1105 packets sent from this host
              0 packets sent with fabricated ip header
              0 output packets dropped due to no bufs, etc.
              0 output packets discarded due to no route
              0 output datagrams fragmented
              0 fragments created
              0 datagrams that can't be fragmented
              0 packets that violated scope rules
              0 multicast packets which we don't join
              Input histogram:
                        TCP: 425
                        UDP: 2406
                        fragment: 138
                        ICMP6: 234
              Mbuf statistics:
                        679 one mbuf
                        two or more mbuf:
                                  lo0= 351
                        2174 one ext mbuf
                        0 two or more ext mbuf
              0 packets whose headers are not continuous
              0 tunneling packets that can't find gif
              0 packets discarded due to too may headers
              0 failures of source address selection
              0 forward cache hit
              0 forward cache miss
              0 packets dropped due to no bufs for control data
    icmp6:
              0 calls to icmp_error
              0 errors not generated because old message was icmp error or so
              0 errors not generated because rate limitation
              Output histogram:
                        echo: 175
                        router solicitation: 70
                        neighbor solicitation: 43
                        neighbor advertisement: 40
                        MLDv2 listener report: 45
              0 messages with bad code fields
              0 messages < minimum length
              0 bad checksums
              0 messages with bad length
              Input histogram:
                        unreach: 5
                        echo reply: 172
                        router advertisement: 8
                        neighbor solicitation: 17
                        neighbor advertisement: 32
              Histogram of error messages to be generated:
                        0 no route
                        0 administratively prohibited
                        0 beyond scope
                        0 address unreachable
                        0 port unreachable
                        0 packet too big
                        0 time exceed transit
                        0 time exceed reassembly
                        0 erroneous header field
                        0 unrecognized next header
                        0 unrecognized option
                        0 redirect
                        0 unknown
              0 message responses generated
              0 messages with too many ND options
              0 messages with bad ND options
              0 bad neighbor solicitation messages
              0 bad neighbor advertisement messages
              0 bad router solicitation messages
              0 bad router advertisement messages
              0 bad redirect messages
              0 path MTU changes
    ipsec6:
              0 inbound packets processed successfully
              0 inbound packets violated process security policy
              0 inbound packets with no SA available
              0 invalid inbound packets
              0 inbound packets failed due to insufficient memory
              0 inbound packets failed getting SPI
              0 inbound packets failed on AH replay check
              0 inbound packets failed on ESP replay check
              0 inbound packets considered authentic
              0 inbound packets failed on authentication
              0 outbound packets processed successfully
              0 outbound packets violated process security policy
              0 outbound packets with no SA available
              0 invalid outbound packets
              0 outbound packets failed due to insufficient memory
              0 outbound packets with no route
    rip6:
              0 messages received
              0 checksum calcurations on inbound
              0 messages with bad checksum
              0 messages dropped due to no socket
              0 multicast messages dropped due to no socket
              0 messages dropped due to full socket buffers
              0 delivered
              0 datagrams output
    pfkey:
              6 requests sent to userland
              352 bytes sent to userland
              histogram by message type:
                        register: 3
                        x_spdadd: 2
                        x_spddump: 1
              0 messages with invalid length field
              0 messages with invalid version field
              0 messages with invalid message type field
              0 messages too short
              0 messages with memory allocation failure
              0 messages with duplicate extension
              0 messages with invalid extension type
              0 messages with invalid sa type
              0 messages with invalid address extension
              7 requests sent from userland
              944 bytes sent from userland
              histogram by message type:
                        register: 3
                        x_spdadd: 2
                        x_spddump: 2
              0 messages toward single socket
              0 messages toward all sockets
              0 messages toward registered sockets
              0 messages with memory allocation failure
    What do you make of it?

  • HT1529 what is my iMac DNS IP address

    What is my iMac DNS IP Address.  I (think) I need it to get my apple TV to work.  I had it working yesterday and today it says NO.  (I did nothing different, except turned it on!!)  It doesn't recognise that I have authorised my iTunes account (several times).

    You can determine your Mac's IP address by opening Sytem Preferences, selecting Network and then selecting the interface you are using to connect to your home network (either Ethernet or WiFi). As for its DNS IP address, the Mac will not have its own DNS address. This will typically be the IP address of the wireless router, if WiFi is being used, or your ISP.
    For your Apple TV to see the Mac, this will use Bonjour to locate the Mac on the local network. So the important thing is that your Mac and the Apple TV are set to the same IP subnet. This is usually the first three sets of numbers in your IP address, while the last number is known as the network address. For example, a Mac with an IP address of 10.0.1.4 has an IP subnet of 10.0.1 and a network address of 4. For other devices using Bonjour to communicate with this Mac, they also need an IP subnet of 10.0.1 but a different network address to 4.
    The other important IP address setting is the router address, aka gateway. For all devices to communicate with each other on a local network, they must have the same router address, which is the IP address of the wireless router or Ethernet switch.
    Now I don't have an Apple TV so I don't know the network settings menu but I would expect that it is set to DHCP, meaning that it is relying on the router to provide it with an IP address. The theory would then go that you would also set the Mac to DHCP so that the router can allocate a dedicated IP address to the Mac and Apple TV and any other device on your network. If any device is set to manual assignment then this could be your issue. Are you able to confirm what network settings the Mac and Apple TV are using and post back here?

Maybe you are looking for