Problem: Sharing Folders with iMac and winXP

We have been running a small workgroup sharing so far two winxp machines over a wifi-modem-router-switch. The two pc share folders without problem.
I have now proudly made the switch over to using Apple iMac. Whilst the iMac experience is fantastic, getting to share the iMac with the rest of the winXP is turning into a nightmare.
I have spent 45 minutes with the tech support team of my ISP router supplier (ISP:Club-Internet - Router :AH4021/Tecom AH4222)
Every check & settings turned out to be fine, but they were unable to diagnose the problem.
I spent 3 sessions and over 1 hour (without counting time waiting over the phone) with the Apple support team, and whilst they were very friendly, they were unable to diagnose the problem.
I cannot ping the iMac from the xp machine, but I am told there is hope though, as i can ping ok my xp machine from iMac.
All firewalls have been removed.
File n window sharing set on all machines.
DHCP manually setup assigning fix IP/DNS etc..
Same username on all machines, with unique machine name
Is there anybody who could help? Help!

Just hanged up from Apple tech support France, and this time, spoke to another friendly AND helpful support assistant named Simon.
Simon got me straight into the Finder>Go>Connect to Server
Type into your Server Address window : smb://and here your pc ip address you want to get to
example: smb://192.168.1.2
Hit Enter key, and your pc should appear
Thank you Simon!
Also, watch out for port 80 being hugged by apps like Skype...it might interfer
AND any port being specified into your NAT configuration in your router might confused the search.
Voila!

Similar Messages

Problems sharing internet with iptables and dnsmasq

I followed this exactly: http://wiki.archlinux.org/index.php/Internet_Share
And here is my dnsmasq.conf
# Configuration file for dnsmasq.
# Format is one option per line, legal options are the same
# as the long options legal on the command line. See
# "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.
# The following two options make you a better netizen, since they
# tell dnsmasq to filter out queries which the public DNS cannot
# answer, and which load the servers (especially the root servers)
# uneccessarily. If you have a dial-on-demand link they also stop
# these requests from bringing up the link uneccessarily.
# Never forward plain names (without a dot or domain part)
#domain-needed
# Never forward addresses in the non-routed address spaces.
#bogus-priv
# Uncomment this to filter useless windows-originated DNS requests
# which can trigger dial-on-demand links needlessly.
# Note that (amongst other things) this blocks all SRV requests,
# so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
# This option only affects forwarding, SRV records originating for
# dnsmasq (via srv-host= lines) are not suppressed by it.
#filterwin2k
# Change this line if you want dns to get its upstream servers from
# somewhere other that /etc/resolv.conf
#resolv-file=
# By default, dnsmasq will send queries to any of the upstream
# servers it knows about and tries to favour servers to are known
# to be up. Uncommenting this forces dnsmasq to try each query
# with each server strictly in the order they appear in
# /etc/resolv.conf
#strict-order
# If you don't want dnsmasq to read /etc/resolv.conf or any other
# file, getting its servers from this file instead (see below), then
# uncomment this.
#no-resolv
# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
# files for changes and re-read them then uncomment this.
#no-poll
# Add other name servers here, with domain specs if they are for
# non-public domains.
#server=/localnet/192.168.0.1
# Example of routing PTR queries to nameservers: this will send all
# address->name queries for 192.168.3/24 to nameserver 10.1.2.3
#server=/3.168.192.in-addr.arpa/10.1.2.3
# Add local-only domains here, queries in these domains are answered
# from /etc/hosts or DHCP only.
#local=/localnet/
# Add domains which you want to force to an IP address here.
# The example below send any host in doubleclick.net to a local
# webserver.
#address=/doubleclick.net/127.0.0.1
# --address (and --server) work with IPv6 addresses too.
#address=/www.thekelleys.org.uk/fe80::20d:60ff:fe36:f83
# You can control how dnsmasq talks to a server: this forces
# queries to 10.1.2.3 to be routed via eth1
# --server=10.1.2.3@eth1
# and this sets the source (ie local) address used to talk to
# 10.1.2.3 to 192.168.1.1 port 55 (there must be a interface with that
# IP on the machine, obviously).
# [email protected]#55
# If you want dnsmasq to change uid and gid to something other
# than root, you will need to have CONFIG_SECURITY_CAPABILITIES
# enabled in your kernel. The default uid and gid of nobody will
# be used if capability is available and this is not set.
#user=
#group=
# If you want dnsmasq to listen for DHCP and DNS requests only on
# specified interfaces (and the loopback) give the name of the
# interface (eg eth0) here.
# Repeat the line for more than one interface.
interface=eth0
# Or you can specify which interface _not_ to listen on
#except-interface=
# Or which to listen on by address (remember to include 127.0.0.1 if
# you use this.)
#listen-address=
# If you want dnsmasq to provide only DNS service on an interface,
# configure it as shown above, and then use the following line to
# disable DHCP on it.
#no-dhcp-interface=
# On systems which support it, dnsmasq binds the wildcard address,
# even when it is listening on only some interfaces. It then discards
# requests that it shouldn't reply to. This has the advantage of
# working even when interfaces come and go and change address. If you
# want dnsmasq to really bind only the interfaces it is listening on,
# uncomment this option. About the only time you may need this is when
# running another nameserver on the same machine.
bind-interfaces
# If you don't want dnsmasq to read /etc/hosts, uncomment the
# following line.
#no-hosts
# or if you want it to read another file, as well as /etc/hosts, use
# this.
#addn-hosts=/etc/banner_add_hosts
# Set this (and domain: see below) if you want to have a domain
# automatically added to simple names in a hosts-file.
#expand-hosts
# Set the domain for dnsmasq. this is optional, but if it is set, it
# does the following things.
# 1) Allows DHCP hosts to have fully qualified domain names, as long
# as the domain part matches this setting.
# 2) Sets the "domain" DHCP option thereby potentially setting the
# domain of all systems configured by DHCP
# 3) Provides the domain part for "expand-hosts"
#domain=thekelleys.org.uk
# Set a different domain for a particular subnet
#domain=wireless.thekelleys.org.uk,192.168.2.0/24
# Same idea, but range rather then subnet
#domain=reserved.thekelleys.org.uk,192.68.3.100,192.168.3.200
# Uncomment this to enable the integrated DHCP server, you need
# to supply the range of addresses available for lease and optionally
# a lease time. If you have more than one network, you will need to
# repeat this for each network on which you want to supply DHCP
# service.
#dhcp-range=192.168.20.100,192.168.20.149,12h
# This is an example of a DHCP range where the netmask is given. This
# is needed for networks we reach the dnsmasq DHCP server via a relay
# agent. If you don't know what a DHCP relay agent is, you probably
# don't need to worry about this.
dhcp-range=192.168.20.100,192.168.20.149,255.255.255.0,12h
# This is an example of a DHCP range with a network-id, so that
# some DHCP options may be set only for this network.
#dhcp-range=red,192.168.0.50,192.168.0.150
# Supply parameters for specified hosts using DHCP. There are lots
# of valid alternatives, so we will give examples of each. Note that
# IP addresses DO NOT have to be in the range given above, they just
# need to be on the same network. The order of the parameters in these
# do not matter, it's permissble to give name,adddress and MAC in any order
# Always allocate the host with ethernet address 11:22:33:44:55:66
# The IP address 192.168.0.60
dhcp-host=00:E0:B8:9C:B7:2C,192.168.20.1
# Always set the name of the host with hardware address
# 11:22:33:44:55:66 to be "fred"
#dhcp-host=11:22:33:44:55:66,fred
# Always give the host with ethernet address 11:22:33:44:55:66
# the name fred and IP address 192.168.0.60 and lease time 45 minutes
#dhcp-host=11:22:33:44:55:66,fred,192.168.0.60,45m
# Give a host with ethernet address 11:22:33:44:55:66 or
# 12:34:56:78:90:12 the IP address 192.168.0.60. Dnsmasq will assume
# that these two ethernet interfaces will never be in use at the same
# time, and give the IP address to the second, even if it is already
# in use by the first. Useful for laptops with wired and wireless
# addresses.
#dhcp-host=11:22:33:44:55:66,12:34:56:78:90:12,192.168.0.60
# Give the machine which says its name is "bert" IP address
# 192.168.0.70 and an infinite lease
#dhcp-host=bert,192.168.0.70,infinite
# Always give the host with client identifier 01:02:02:04
# the IP address 192.168.0.60
#dhcp-host=id:01:02:02:04,192.168.0.60
# Always give the host with client identifier "marjorie"
# the IP address 192.168.0.60
#dhcp-host=id:marjorie,192.168.0.60
# Enable the address given for "judge" in /etc/hosts
# to be given to a machine presenting the name "judge" when
# it asks for a DHCP lease.
#dhcp-host=judge
# Never offer DHCP service to a machine whose ethernet
# address is 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,ignore
# Ignore any client-id presented by the machine with ethernet
# address 11:22:33:44:55:66. This is useful to prevent a machine
# being treated differently when running under different OS's or
# between PXE boot and OS boot.
#dhcp-host=11:22:33:44:55:66,id:*
# Send extra options which are tagged as "red" to
# the machine with ethernet address 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,net:red
# Send extra options which are tagged as "red" to
# any machine with ethernet address starting 11:22:33:
#dhcp-host=11:22:33:*:*:*,net:red
# Ignore any clients which are specified in dhcp-host lines
# or /etc/ethers. Equivalent to ISC "deny unkown-clients".
# This relies on the special "known" tag which is set when
# a host is matched.
#dhcp-ignore=#known
# Send extra options which are tagged as "red" to any machine whose
# DHCP vendorclass string includes the substring "Linux"
#dhcp-vendorclass=red,Linux
# Send extra options which are tagged as "red" to any machine one
# of whose DHCP userclass strings includes the substring "accounts"
#dhcp-userclass=red,accounts
# Send extra options which are tagged as "red" to any machine whose
# MAC address matches the pattern.
#dhcp-mac=red,00:60:8C:*:*:*
# If this line is uncommented, dnsmasq will read /etc/ethers and act
# on the ethernet-address/IP pairs found there just as if they had
# been given as --dhcp-host options. Useful if you keep
# MAC-address/host mappings there for other purposes.
#read-ethers
# Send options to hosts which ask for a DHCP lease.
# See RFC 2132 for details of available options.
# Common options can be given to dnsmasq by name:
# run "dnsmasq --help dhcp" to get a list.
# Note that all the common settings, such as netmask and
# broadcast address, DNS server and default route, are given
# sane defaults by dnsmasq. You very likely will not need
# any dhcp-options. If you use Windows clients and Samba, there
# are some options which are recommended, they are detailed at the
# end of this section.
# Override the default route supplied by dnsmasq, which assumes the
# router is the same machine as the one running dnsmasq.
#dhcp-option=3,1.2.3.4
# Do the same thing, but using the option name
#dhcp-option=option:router,1.2.3.4
# Override the default route supplied by dnsmasq and send no default
# route at all. Note that this only works for the options sent by
# default (1, 3, 6, 12, 28) the same line will send a zero-length option
# for all other option numbers.
#dhcp-option=3
# Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5
#dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5
# Set the NTP time server address to be the same machine as
# is running dnsmasq
#dhcp-option=42,0.0.0.0
# Set the NIS domain name to "welly"
#dhcp-option=40,welly
# Set the default time-to-live to 50
#dhcp-option=23,50
# Set the "all subnets are local" flag
#dhcp-option=27,1
# Send the etherboot magic flag and then etherboot options (a string).
#dhcp-option=128,e4:45:74:68:00:00
#dhcp-option=129,NIC=eepro100
# Specify an option which will only be sent to the "red" network
# (see dhcp-range for the declaration of the "red" network)
# Note that the net: part must precede the option: part.
#dhcp-option = net:red, option:ntp-server, 192.168.1.1
# The following DHCP options set up dnsmasq in the same way as is specified
# for the ISC dhcpcd in
# http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt
# adapted for a typical dnsmasq installation where the host running
# dnsmasq is also the host running samba.
# you may want to uncomment some or all of them if you use
# Windows clients and Samba.
#dhcp-option=19,0 # option ip-forwarding off
#dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
#dhcp-option=45,0.0.0.0 # netbios datagram distribution server
#dhcp-option=46,8 # netbios node type
# Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client
# probably doesn't support this......
#dhcp-option=option:domain-search,eng.apple.com,marketing.apple.com
# Send RFC-3442 classless static routes (note the netmask encoding)
#dhcp-option=121,192.168.1.0/24,1.2.3.4,10.0.0.0/8,5.6.7.8
# Send vendor-class specific options encapsulated in DHCP option 43.
# The meaning of the options is defined by the vendor-class so
# options are sent only when the client supplied vendor class
# matches the class given here. (A substring match is OK, so "MSFT"
# matches "MSFT" and "MSFT 5.0"). This example sets the
# mtftp address to 0.0.0.0 for PXEClients.
#dhcp-option=vendor:PXEClient,1,0.0.0.0
# Send microsoft-specific option to tell windows to release the DHCP lease
# when it shuts down. Note the "i" flag, to tell dnsmasq to send the
# value as a four-byte integer - that's what microsoft wants. See
# http://technet2.microsoft.com/WindowsServer/en/library/a70f1bb7-d2d4-49f0-96d6-4b7414ecfaae1033.mspx?mfr=true
#dhcp-option=vendor:MSFT,2,1i
# Send the Encapsulated-vendor-class ID needed by some configurations of
# Etherboot to allow is to recognise the DHCP server.
#dhcp-option=vendor:Etherboot,60,"Etherboot"
# Send options to PXELinux. Note that we need to send the options even
# though they don't appear in the parameter request list, so we need
# to use dhcp-option-force here.
# See http://syslinux.zytor.com/pxe.php#special for details.
# Magic number - needed before anything else is recognised
#dhcp-option-force=208,f1:00:74:7e
# Configuration file name
#dhcp-option-force=209,configs/common
# Path prefix
#dhcp-option-force=210,/tftpboot/pxelinux/files/
# Reboot time. (Note 'i' to send 32-bit value)
#dhcp-option-force=211,30i
# Set the boot filename for netboot/PXE. You will only need
# this is you want to boot machines over the network and you will need
# a TFTP server; either dnsmasq's built in TFTP server or an
# external one. (See below for how to enable the TFTP server.)
#dhcp-boot=pxelinux.0
# Boot for Etherboot gPXE. The idea is to send two different
# filenames, the first loads gPXE, and the second tells gPXE what to
# load. The dhcp-match sets the gpxe tag for requests from gPXE.
#dhcp-match=gpxe,175 # gPXE sends a 175 option.
#dhcp-boot=net:#gpxe,undionly.kpxe
#dhcp-boot=mybootimage
# Encapsulated options for Etherboot gPXE. All the options are
# encapsulated within option 175
#dhcp-option=encap:175, 1, 5b # priority code
#dhcp-option=encap:175, 176, 1b # no-proxydhcp
#dhcp-option=encap:175, 177, string # bus-id
#dhcp-option=encap:175, 189, 1b # BIOS drive code
#dhcp-option=encap:175, 190, user # iSCSI username
#dhcp-option=encap:175, 191, pass # iSCSI password
# Test for the architecture of a netboot client. PXE clients are
# supposed to send their architecture as option 93. (See RFC 4578)
#dhcp-match=peecees, option:client-arch, 0 #x86-32
#dhcp-match=itanics, option:client-arch, 2 #IA64
#dhcp-match=hammers, option:client-arch, 6 #x86-64
#dhcp-match=mactels, option:client-arch, 7 #EFI x86-64
# Do real PXE, rather than just booting a single file, this is an
# alternative to dhcp-boot.
#pxe-prompt="What system shall I netboot?"
# or with timeout before first available action is taken:
#pxe-prompt="Press F8 for menu.", 60
# Available boot services. for PXE.
#pxe-service=x86PC, "Boot from local disk", 0
# Loads <tftp-root>/pxelinux.0 from dnsmasq TFTP server.
#pxe-service=x86PC, "Install Linux", pxelinux
# Loads <tftp-root>/pxelinux.0 from TFTP server at 1.2.3.4.
# Beware this fails on old PXE ROMS.
#pxe-service=x86PC, "Install Linux", pxelinux, 1.2.3.4
# Use bootserver on network, found my multicast or broadcast.
#pxe-service=x86PC, "Install windows from RIS server", 1
# Use bootserver at a known IP address.
#pxe-service=x86PC, "Install windows from RIS server", 1, 1.2.3.4
# If you have multicast-FTP available,
# information for that can be passed in a similar way using options 1
# to 5. See page 19 of
# http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
# Enable dnsmasq's built-in TFTP server
#enable-tftp
# Set the root directory for files availble via FTP.
#tftp-root=/var/ftpd
# Make the TFTP server more secure: with this set, only files owned by
# the user dnsmasq is running as will be send over the net.
#tftp-secure
# Set the boot file name only when the "red" tag is set.
#dhcp-boot=net:red,pxelinux.red-net
# An example of dhcp-boot with an external TFTP server: the name and IP
# address of the server are given after the filename.
# Can fail with old PXE ROMS. Overridden by --pxe-service.
#dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3
# Set the limit on DHCP leases, the default is 150
#dhcp-lease-max=150
# The DHCP server needs somewhere on disk to keep its lease database.
# This defaults to a sane location, but if you want to change it, use
# the line below.
#dhcp-leasefile=/var/lib/misc/dnsmasq.leases
# Set the DHCP server to authoritative mode. In this mode it will barge in
# and take over the lease for any client which broadcasts on the network,
# whether it has a record of the lease or not. This avoids long timeouts
# when a machine wakes up on a new network. DO NOT enable this if there's
# the slighest chance that you might end up accidentally configuring a DHCP
# server for your campus/company accidentally. The ISC server uses
# the same option, and this URL provides more information:
# http://www.isc.org/index.pl?/sw/dhcp/authoritative.php
#dhcp-authoritative
# Run an executable when a DHCP lease is created or destroyed.
# The arguments sent to the script are "add" or "del",
# then the MAC address, the IP address and finally the hostname
# if there is one.
#dhcp-script=/bin/echo
# Set the cachesize here.
#cache-size=150
# If you want to disable negative caching, uncomment this.
#no-negcache
# Normally responses which come form /etc/hosts and the DHCP lease
# file have Time-To-Live set as zero, which conventionally means
# do not cache further. If you are happy to trade lower load on the
# server for potentially stale date, you can set a time-to-live (in
# seconds) here.
#local-ttl=
# If you want dnsmasq to detect attempts by Verisign to send queries
# to unregistered .com and .net hosts to its sitefinder service and
# have dnsmasq instead return the correct NXDOMAIN response, uncomment
# this line. You can add similar lines to do the same for other
# registries which have implemented wildcard A records.
#bogus-nxdomain=64.94.110.11
# If you want to fix up DNS results from upstream servers, use the
# alias option. This only works for IPv4.
# This alias makes a result of 1.2.3.4 appear as 5.6.7.8
#alias=1.2.3.4,5.6.7.8
# and this maps 1.2.3.x to 5.6.7.x
#alias=1.2.3.0,5.6.7.0,255.255.255.0
# and this maps 192.168.0.10->192.168.0.40 to 10.0.0.10->10.0.0.40
#alias=192.168.0.10-192.168.0.40,10.0.0.0,255.255.255.0
# Change these lines if you want dnsmasq to serve MX records.
# Return an MX record named "maildomain.com" with target
# servermachine.com and preference 50
#mx-host=maildomain.com,servermachine.com,50
# Set the default target for MX records created using the localmx option.
#mx-target=servermachine.com
# Return an MX record pointing to the mx-target for all local
# machines.
#localmx
# Return an MX record pointing to itself for all local machines.
#selfmx
# Change the following lines if you want dnsmasq to serve SRV
# records. These are useful if you want to serve ldap requests for
# Active Directory and other windows-originated DNS requests.
# See RFC 2782.
# You may add multiple srv-host lines.
# The fields are <name>,<target>,<port>,<priority>,<weight>
# If the domain part if missing from the name (so that is just has the
# service and protocol sections) then the domain given by the domain=
# config option is used. (Note that expand-hosts does not need to be
# set for this to work.)
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 289
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 289 (using domain=)
#domain=example.com
#srv-host=_ldap._tcp,ldapserver.example.com,389
# Two SRV records for LDAP, each with different priorities
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2
# A SRV record indicating that there is no LDAP server for the domain
# example.com
#srv-host=_ldap._tcp.example.com
# The following line shows how to make dnsmasq serve an arbitrary PTR
# record. This is useful for DNS-SD. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for PTR records.)
#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"
# Change the following lines to enable dnsmasq to serve TXT records.
# These are used for things like SPF and zeroconf. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for TXT records.)
#Example SPF.
#txt-record=example.com,"v=spf1 a -all"
#Example zeroconf
#txt-record=_http._tcp.example.com,name=value,paper=A4
# Provide an alias for a "local" DNS name. Note that this _only_ works
# for targets which are names from DHCP or /etc/hosts. Give host
# "bert" another name, bertrand
#cname=bertand,bert
# For debugging purposes, log each DNS query as it passes through
# dnsmasq.
#log-queries
# Log lots of extra information about DHCP transactions.
#log-dhcp
# Include a another lot of configuration options.
#conf-file=/etc/dnsmasq.more.conf
#conf-dir=/etc/dnsmasq.d
eth0 is set up for 192.168.20.1, netmask 255.255.255.0. I can get an IP from my client machine and ping 192.168.20.1, but cannot access the internet. resolv.conf on the client machine has a nameserver of 192.168.20.1. Also, Firefox time sout trying to access Google via it's static IP.
What should I do to grant the internet to my client machine?

http://wiki.archlinux.org/index.php/DNS_with_bind -> Did you try it too ?

My host name changes every few days, since Xmas adding a macbook its changed 6 times. Do I need to stop this? Does it cause problems with sharing between the iMac and macbook?

my host name changes every few days, since Xmas adding a macbook its changed 6 times. Do I need to stop this? Does it cause problems with sharing between the iMac and macbook?

There are several possible causes for this problem.
1. Two (or more) computers on the local network have the same Bonjour name, such as "X's-MacBook-Pro.local".
2. You have two simultaneous connections to the same local network: probably Ethernet and Wi-Fi. If applicable, disconnect the Ethernet cable or turn off Wi-Fi.
3. A Mac wakes from sleep due to network traffic. This is due to a bug in OS X that may only affect some models.
4. 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.
5. A third-party wireless router has incompatible settings or firmware. In that case, refer to the manufacturer or ISP for support. Restarting the router may help, temporarily.
6. See also this support article.
Rename the computer in the Sharing preference pane.

Can't see shared folders with smbnetfs

Hi!
I'm having trouble with smbnetfs. i installed it successfully, but the folder where the shares should be mounted is always empty
I can mount folders with smbmount and there are no problems but i would like to be able to see all the shared folders...
can somebody help me?
thanks!

Just to dig in deeper with this. I'm having a similar problem (perhaps the same) as described above.
I'm using smbnetfs to mount a folder in my home directory to be my network neighbourhood. When I open it in pcmanfm I can see the work groups, and upon opening a workgroup it'll show nothing more. But in fact, when you open the terminal and do a ls -a you'll notice there are in fact folders corresponding to your computers in that workgroup. Browsing any further works flawlessly.
It's however a minor annoyance that pcmanfm doesn't seem to show them (you can however add a slash to your navigation bar and they'll show up there, rather weird). Has anyone found a way to solve that?

I have two Apple IDs - one associated with iPad and iPhone and the other associated with iMac and MacAir. I am going to lose the former e-mail address imminently and would like to associate all devices with just one ID. How do I do this? Thanks

I have two Apple IDs - one associated with iPad and iPhone and the other associated with iMac and MacAir. I am going to lose the former e-mail address imminently and would like to associate all devices with just one ID. How do I do this? Thanks

Thanks - I guess it is like there were two of me!
I bought the iPhone first and it seemed natural to link it to the (work) e-mail address which was in constant use. The iMac for home use came next and it seemed natural to use my home e-mail address, particularly as I knew by then that I would lose the work address after my imminent retirement. The same logic went for the recent puchase of the MacAir. I am not sure what happened with the iPad (also a recent purchase) - iTunes seemed to puch me towards the same ID as the iPhone.
It is not a huge problem - just makes my persona look schizoid! Otherwise very happy with everything Apple.

Are there any known compatibility issues with iMac and Google Chrome?

Does anyone know of any compatibility issues with iMac and Google chrome. A Facebook friend who is a photographer posted recently that Chrome had ruined his iMac. He stead that it ran an update on itself that made safari and chrome unusable - slow running overall. In the end he had to reinstall his OS.
Is anyone aware of this and should I un-install Chrome off my Mac?
Thanks,
S.

There is nothing official but your post will attract a variety of personal experiences. I once loaded Chrome and found myself with the dreaded MacKeeper malware, loads of pop ups and conflicts with my system. Part of the problem is the huge range of add ons you are tempted to take on, many of which are not as strictly tested as Apple extensions. I would say, unless you have a specific reason, leave it alone. The best browser is Firefox and for Macs, Safari is OK.

I am new with iMac and I am trying to copy some file from my external HDD but it does not let me also I can't delete anything from this HDD using the finder. Can somebody help me , please?

I am new with iMac and I am trying to copy some file from my external HDD that a used with my PC but it does not let me also I can't delete anything from this HDD using the finder. Can somebody help me , please?

No, unfortunately, when you format a drive, it will erase all the contents. So you will need to find a temporary "storage" place to put the stuff using a PC so you have access to it. Then reformat using Disk Utility (Applications > Utilities). If only using with mac, format Mac OS Extended (Journaled) and use GUID Partition scheme under Partitions/Options. After formatting, you can drag the files back.

Any Problems using SSL with Safari and the move with Internet explorer to require only TLS encryption.

Any Problems using SSL with Safari and the move with Internet explorer to require only TLS encryption.

Hi .
Apple no longer supports Safari for Windows if that's what you are asking > Apple apparently kills Windows PC support in Safari 6.0
Microsoft has not written IE for Safari for many years.

LR 4 RC2 ...vexing problem, 3 sessions with support and still not able to find? With all settings re

LR 4 RC2 ...vexing problem, 3 sessions with support and still not able to find? With all settings reset and running a test catalog a raw image when opened in develop will when imediately going back to library view show a significant color shift in red, orange and purple but only in images with significant content in those colors. at first the culprit appeared to be camera calibration default but not reproducable. The problem exists even when opening older images from months ago? Also if second screen running in loupe mode the image is not shifted.
Any ideas please
Dave

Jim01403, Geoff and others...I'm new here so I'll need a little time The thread is very interesting, populated by serious mature people, how refreshing! It clearly is part of what i'm experiencing and is answered answered here...thank you. My main problem is still the significant color shift between develope and library modules. I'll attach one from each so you and others can see. Unfortunately the library version is the bad one so printing is now very problematic...Note, this occurs in either single or with second monitor on the library version is displayed. I have reset virtually everything and wonder if a cache is not updating or color space is not matching? A symptom/detail worth noting, when switching to library mode, the correct image is displayed for about a second then it jumps to what you see in the examples. As if the library module starts to rendering from develope settings then jumps tback to the original inedited preview??
Maybe just go back to 3.6 and tread water till 4.1 is fixed?
Dave

Is Samsung Galaxy 4 compatible with iMac and other Apple products?

Is Samsung Galaxy 4 compatible with iMac and other Apple products?

Yes, the s4 is compatible with music and photo transfers between your imac. I don't have experience with the cloud, but it should be the exact same thing.
Now, there will be a few differences between how you get the files onto said device. With the iPhone, you may be able to do it wirelessly, but with the s4 you will have to plug it in.
The s4 will not work with iLife or iLife applications either. However, bigger screen, more customizable ui and experience with samsung phones personally, I would recommend the s4 over the iPhone 5.
Finally iMac

Problem accessing shared folders with SMB from a Windows machine

When I reboot my Macmini, I cant access the shared folders from any Windows machine. On the Windows machine, I'm being prompted for my password, but event re-entering my password does help to get access.
The workaround I found is to go to the MacOSX System Preferences, Sharing, File Sharing, Options, and to uncheck and re-check the checkbox Share file and folders using SMB (Windows). Then I can access again the shared forders from a Windows machine and I'm not re-prompted for my password.
This is quite trooblesome to do that everytime I reboot my Mac. Is anybody experiencing the same pb? Any idea to fix it?
Also, since Lion, I'm experiencing some connection interruption, especially when copying big files from my Mac to a Windows machine.

Yes that is basically the only workaround for this problem. By chance do you have a SSD installed in the Mini?
I had this problem on my MBP when I had a SSD installed. Problem goes away with the original drive or a Seagate XT series drive.
If you don't have a SSD installed the only other option is to Wipe the drive and reinstall and test (Make a TM backup first so you can restore if the problem continues with the clean Re-Install).
JosoSG wrote:
When I reboot my Macmini, I cant access the shared folders from any Windows machine. On the Windows machine, I'm being prompted for my password, but event re-entering my password does help to get access.
The workaround I found is to go to the MacOSX System Preferences, Sharing, File Sharing, Options, and to uncheck and re-check the checkbox Share file and folders using SMB (Windows). Then I can access again the shared forders from a Windows machine and I'm not re-prompted for my password.
This is quite trooblesome to do that everytime I reboot my Mac. Is anybody experiencing the same pb? Any idea to fix it?
Also, since Lion, I'm experiencing some connection interruption, especially when copying big files from my Mac to a Windows machine.

Sharing Folders with single users and Teams?

Will there be an option to share folders with single users and teams. Something like DropBox in the near future?

Yes - the ability to share folders will be coming in a future release. Stay tuned!
thanks,
Todd

Networking\Sharing: Drive resourse with Imac and Windows PCs

May question start with how dose a person share an IMac external USB drives\resourses with a windows systems.

Hi Dennis,
I tried the steps provided but when I attempted to connect the two computers my iMac said it had to shutdown and had a series of error codes it wanted me to send to apple.
If I follow these steps successfully will I be able to copy or pull files from the windows machine onto the iMac? We have lots of pictures and word files that I'd like to transfer onto the iMac and into programs like iPhoto and Word for Mac.
Is there any other programs required to get the two machines to share files other than what is on both computers?
Thanks, Roger

Can't see shared folders with AFP protocol

Hi,
I have an home network, with 2 iMac and a Netgear (DG834PN) router.
When I try to share a folder with AFP protocol (Preferences > Sharing > Sharing documents),
I can't see it from other computer.

Just to dig in deeper with this. I'm having a similar problem (perhaps the same) as described above.
I'm using smbnetfs to mount a folder in my home directory to be my network neighbourhood. When I open it in pcmanfm I can see the work groups, and upon opening a workgroup it'll show nothing more. But in fact, when you open the terminal and do a ls -a you'll notice there are in fact folders corresponding to your computers in that workgroup. Browsing any further works flawlessly.
It's however a minor annoyance that pcmanfm doesn't seem to show them (you can however add a slash to your navigation bar and they'll show up there, rather weird). Has anyone found a way to solve that?

Sharing folders with Samba in Mavericks

Hi,
I've spent the whole afternoon trying to access some shared folders of my MacBook Pro from a machine running Ubuntu 12.04 using samba. is it possible? I read AFP is deprecated and SMB2 is going to be the standard protocol. I also read SMB2 is getting some compatiblities problems because it is unstable so far, and that a possible workaround is to force smbd to use the old SMB1. I have been succeed connecting from a Windows PC to the MacBook Pro using both protocols: SMB and AFP, but with a Ubuntu PC only with the second option. Again, is it possible to access my shared mac's resource using SMB? if AFP is pretended to disappear, how I will access my folders from a linux PC?
Thanks

Yes - the ability to share folders will be coming in a future release. Stay tuned!
thanks,
Todd

Problem: Sharing Folders with iMac and winXP

Similar Messages

Maybe you are looking for