File sharing network problem

I have an Airport Extreme (G) base station with an Airport Express acting as a WDS extender. I have two client Macs - a 24" iMac (Intel Dual Core) and an iBook (G4). There are a variety of other clients as well - 2 wireless-G tivos, a Win XP laptop, a wireless ethernet bridge serving a slingbox.
My problem is with the two Macs. Using Network browser, from the iMac, I can connect to the iBook just fine via AFP. However, when I try to connect to the iMac from the iBook, it tries to use FTP, then I get the error "unable to find alias." Both macs have AppleTalk enabled and both have File Sharing enabled.
I suspect that the root of the problem may be from the fact that the iMac was set up by copying everything over from an older iMac FP (I've learned my lesson and will not use the Migration Assistant again!). But, I can't figure out how to correct this.
Thanks!

Hi franki, I'm glad those web sites were useful.
Unfortunately I can't advise about your remaining problem because I don't have a suitable Windows computer to try things out on. Maybe somebody else here can.
I'd suggest you give a few more details about exactly how far you get and at which point things get stuck.
Also, if nobody on this board can help then you could try another one. There are several boards here related to networking, of which the Tiger Forums Getting Online & Networking one seems to be the most lively.
MacBook (OS 10.4.8) iMac G4 (OS 10.3.9)

Similar Messages

Screen Sharing/network problem seems confined to 1 volume. What's the fix?

I am having a networking problem on one of the volumes of my multi-volumed, three-Mac local area network, and I need a networking guru to identify the specific software file(s), application(s), or system configuration that is the cause of the problem. I have already spent several hours checking and re-checking the various hardware and system preference settings involved, and I have narrowed the problem down to a software corruption issue and/or system configuration issue on one volume.
I now need someone to identify specifically what the nature of the problem is, and how to eliminate it. I am not looking for a sledgehammer solution that says I should re-install all of the Mac OS X software on the problem volume. That may be held in reserve as a last resort. I'm looking for a more elegant approach, one that points out the specific corrupt files to remove without disturbing everything else.
Here's some background to set the context. I have a MacBook Pro laptop; a PowerMac iMac G5; and a PowerMac G4 hooked up in a network. All are running Leopard 10.5.8. All have file sharing and screen sharing enabled. Besides being able to connect to each other using registered users, my goal here is for each of the Macs to be able to share the screen of the others upon my demand. Since each of the 3 Macs can theoretically share the screens of the other 2, that makes a total of six possible connections. Five succeed; one does not. That's the problem. I am trying to determine why the iMac G5 cannot share the screen of the MacBook Pro.
The iMac G5 has no problem sharing the screen of the PowerMac G4. That connection is fast and immediate. But, every time that I hit the Share Screen button on the iMac G5 to try to connect to the MacBook Pro, I get a window with the blue barber pole spinning for two or three minutes as it is allegedly "Connecting to Mac Book Pro," followed by a window with a headline telling me that "Connection Failed to MacBook Pro." The text within that window goes on to say: "Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer to which you are attempting to connect. Also make sure that your network connection is working properly."
Well, as I indicated, the PowerMac G4 has no problem sharing the screen of the MacBook Pro, so the Screen Sharing settings on the laptop are correct; and the iMac G5 can share the screen of the PowerMac G4, so its network connection is working properly in that regard. It is only in regards to sharing the screen of the MacBook Pro that the iMac G5 is not working properly.
The reason why I say that the issue must be unique to the one volume in question, let's call it "iMacG5 Music," is that another Leopard volume on the same computer has no problem whatsoever in sharing the screen of the MacBook Pro. Whenever I boot up in that volume, let's call it "iMacG5 JMB," it makes a network connection with a registered user name immediately, and it is able to share the screen of the MacBook Pro within a second of my issuing the command. In sharp contrast to the success of the iMacG5 JMB volume, the iMacG5 Music is unacceptably slow (several minutes slow!) in making a network connection with the MacBook Pro, and it always fails to share the screen of the MacBook Pro, preferring instead to take about three minutes to attempt the connection, before announcing its failure.
Since the iMacG5 Music volume makes an immediate network connection to the PowerMac G4, as well as sharing the screen of the PowerMac G4 the moment I ask it to, I have concluded that the hardware of the iMac G5 is just fine. The problem seems confined to the system software and/or associated networking files that are unique to the iMacG5 Music volume. I just don't know what those files could be, or where the problem lies, so I've issued this call for help.
Let me add one more little twist to this puzzle which baffles me even more. I use external LaCie Firewire drives as clone backups of my Macs. As part of my trouble-shooting process, I booted up from the cloned versions of the iMacG5 JMB volume and the iMacG5 Music volume. What I learned surprised me!
The iMacG5 JMB clone worked just fine in making a fast network connection to the MacBook Pro, as well as sharing the screen of the MacBook Pro. I expected that. What I did not expect was that the iMacG5 Music clone was also able to make a fast network to the MacBook Pro, as well as share its screen!
Yes, that's right. It's weird! Screen sharing works OK when I start-up from the clone of the iMacG5 Music volume, but it does not succeed when I boot up on the source itself! I was surprised to find that out, but I'm glad I did.
(Over the past few days since I executed the last clone, I did use Drive Genius to de-frag the source volume, and maybe that has contributed to the problem I am now encountering. But it's hard to say, since nothing else seems to be amiss.)
One solution, I suppose, would be to sync the clone back to the source. But, before I do that, I'm just wondering if anyone has a clue as to the nature of this problem on the source volume and what I might do to remedy it—short of re-installing the system software or restoring from the clone. Anyone have any insight to this problem?

CORRECTION #2:
Ignore the previous "CORRECTION" post.
Oops, excuse me, I wrote that sentence correctly the first time.
I was trying to point out that the ability of the iMac G5 computer to connect quickly and effectively to the PowerMac G4 when booted up into the iMacG5 Music volume was an indication (to me, anyway) that there is nothing wrong with the computer's hardware, nor its network connection ability, but that the problem lay somewhere in the files/settings used to connect to the MacBook Pro, which it cannot accomplish.
This is what happens when I get engrossed in one of these technical morasses and it ***** me into its vortex all through the night... time for bed.

Personal file sharing has problems...

I have a very plain, basic network here at home. I have a 8 port switch that connects all of my computers to my network. These include several that are connected wirelessly (2 ibooks, MacBook, PowerBook) and 2 wired connections in a Mac Pro and a Digital Audio 466 Power Mac. All are running 10.4.8. Until just recently I have been able to file share between all computers without problems. Now I cannot connect to or from the Power Mac through any file sharing. The Power Mac has no problems accessing the internet nor do I problems observing the PowerMac with Apple Remote Desktop.
I have checked all network/sharing settings and can't seem to find anything out of the ordinary.
Any ideas?
Paxx

Hi,
In System Preferences/Sharing, has the "Personal
File Sharing" checkbox been un-checked? Or has a
firewall been turned on on the PowerMac ?
Are there any errors in system.log in
/var/log ?
Also, are there any errors posted in
AppleFileServiceError.log in
/Library/Log/AppleFileService ?
Ed
PB G4 Mac OS X
(10.3.9) PM G4 Dual 1.25, PM G4 Dual 867, OSX
10.2.8, OSX Server 10.2.8
Ed, thanks for the suggestions I will have a look tomorrow. System prefs I know are right but didn't think to see if there has been a firewall or errors posted in the logs. thanks for the suggestions.

File Sharing Permissions Problem When NEW Files Created

My wife & I have a home office network setup for our business, and are having trouble with shared files over the network. We're both on Macs, and all of our client files reside on an internal hard drive in my Mac Pro. I've set her up as a "Sharing Only" user on my computer (which matches the username & password of her account on her iMac), and have properly setup file sharing in both the System Preferences, and in the directory itself that we want shared. I've also applied the permissions to all files & folders below the main folder, and she can view, open and save whatever she needs and it works great.
*Here's where the problem comes in...* If either of us create a NEW file or folder, the other person doesn't have WRITE access to it (we can browse and open it fine). The second I go to update a file she created, it won't let me over-write it, and I have to go into the permissions for that specific file and give myself Read/Write access. I've experimented with "Groups", and assigned both of us a special group, and applied that group access to that directory, but it doesn't make any difference when a NEW file or folder is created - it doesn't copy the parent directory permissions to itself, it makes one of us the owner, and nobody else has access.
Is there any way around this? We're both constantly creating new files, and it really hampers our workflow to have to keep re-applying file permissions every time one of us creates something new. Ideally, any new files created within that main client folder would automatically have the same permissions as the parent directory. Any help would be greatly appreciated! Thanks!!

Here's how to do this with Access Control Lists.
1) Go to System Preferences -> Accounts. Unlock the padlock. Click the + button. Make a new group. Call this group "sharing" for the purposes of this exercise. Add the users you want to the group.
2) Make a new empty folder in /Users/Shared. Call it "sharefolder".
3) Log in to an admin account and paste all three of these lines at once into Terminal:
sudo chmod +a "sharing allow delete,chown,list,search,add_file,\
addsubdirectory,delete_child,file_inherit,directoryinherit" \
/Users/Shared/sharefolder
4) From now on, any files you create or copy to the sharefolder or to any of its subfolders will inherit read+write permission for all users in the group. If you have any existing files that you want to move into the sharefolder, a simple move by drag & drop won't cause the permissions to propagate. you need to hold down the option key while dragging them in. This will copy them over, ensuring that the ACL permission is properly inherited.
One other caveat: Files created by a small number of OS X apps won't inherit the permissions properly if saved directly into the ACL folder hierarchy. TextEdit is one such app. Save TextEdit files in a temporary location first, and then copy them in. Then they will have the correct permissions.

Personal File Sharing + FileVault = Problems?

Hello, sorry my poor english.
I have enabled 'Personal File Sharing' and I have a small index.html file on my 'Sites' folder.
When I try to check my webpage using the supplied link...
http://localhost/~MyUserName/
I get this error (403 Forbidden):
You don't have permission to access /~MyUserName/ on this server.
so I checked Apache's Error Log and this is the info I have got:
(13)Permission denied: access to /~MyUserName/ failed because search permissions are missing on a component of the path
I have already run 'Disk Utility' and repaired all permissions but still no go.
Could it be because I have FileVault enabled on this account? If I create a user and leave the filevault off, the whole thing works just fine! I would like to keep my setup as it is now but to be able to view my pages locally. Is there a work around this problem between the Apache server and the FileVault?
Thank you.

Problem solved.
What I did was to change the permissions to ~MyUserName by control-clicking it in the Finder, choosing Get Info from the menu which appears, looking at the Ownership & Permissions section and setting the Others item to Read Only.
But I've learned something interesting, I can only change the 'Others' field on ~MyUserName by control-clicking on ~MyUserName from Finder's left menu! If I do it from Macintosh HD, then Users, then control-clicking ~MyUserName icon, all options are grayed out (doesn't make much sense, I first thought it was because I have FileVault enabled).
Now everything is working.

Domain users files sharing permission problem

Dear Domain Professional,
We have a three domain controllers 192.168.92 .162,167,150 All domain controller working with
Global Catalog servers ( Root forest ) . All domain controller live synchronize with each others like Users , Group policy , ADS, DNS.
lastnight we had a problem with file sharing permission . it had been asked username & password . why this problem was happened ?
Finally we had restated with all domain controller then file sharing perfectly working fine .i had verified all events in domain controller there is no any error issue .
Note:- we are using juniper firewall is there any security issue ?
happended
Regards
Subash

Hi,
According to the
repadmin results, there isn’t any replication issue.
I was wondering how long did the issue last until reboots of DCs?
If the period is short, then this behavior is normal, because AD replication takes time, this issue could occur before AD replication has completed.
Another possible cause is related to Kerberos authentication and authorization mechanism.
During a logon session, once a user has been authenticated successfully, it gets an
access token containing its SID and group membership and privileges.
The user's access token is subsequently inherited by any application process that the user starts during the logon session.
If we change user’s group membership and privileges
after the access token has been issued, the changes won’t be updated until this user logs off and logs on again.
Here are some related articles below for your references:
How Access Tokens Work
http://technet.microsoft.com/en-us/library/cc783557(v=WS.10).aspx
How the Kerberos Version 5 Authentication Protocol Works
http://technet.microsoft.com/en-us/library/cc772815(v=ws.10).aspx
I hope this helps.
Amy

File sharing permission problem

i have two machines, an iMac and MacBook Pro both running 10.5.6, and am trying to access (via standard file sharing) files residing on the iMac from the MBP. i log in with correct credentials. when i do a Get Info for the file resident on the iMac from the MBP, the file's permissions are incorrect. in fact, if i perform this same operation several times, i get different results, even though the source file is not being touched. the actual perms are rw-rw-r-- with group "media". the displayed perms are always rw-r--r--; the group name is sometimes "staff", sometimes "media".
i'm simply trying to copy files to the MBP from the iMac, wanting to retain permissions. they are always getting messed up.
anyone had any luck in simply copying files from one machine to another and retaining permissions?

on further investigation, perms are just wrong. sometimes the user is incorrect. if i add extended perms (via ACLs), they just don't appear at all.
is this just a bad leopard bug?

File Sharing Password problem

Hi: In Storage and Sharing I have File Sharing and Wi-Wi Sharing turned on. I never noticed that the Password Protect was turned on. I never set a password but now that I want to use it the PB is demanding a password - which I have not got.
Is there any way around this or do I have to do a Security wipe?
Thanks.
Donald

Try a number of your common passwords to see if you can get past it. Try your BBID Password. If you didn't set the password, someone must have had access to your PlayBook and set one. Check with your friends or coworkers. If you have to do a wipe, do a backup first. I don't know of any way around this situation. If you work with jerks, you will have to set a password to keep them out.

How do I setup a wireless file sharing network with a desktop and laptop?

Here are the specs.
Desktop, 1 Ethernet, hooked to Wireless router and is my main computer. XP Professional
Router, Wireless Linksys WRT54GL
Laptop, Wireless card and Ethernet. XP Home
Both the Desktop and Laptop can use the internet. The internet can be accessed by both computers. I have tried everything from creating a network via windows, messed with that for a couple days, tried programs and messed with them for a few hours.
I can sometimes see the other computer, when I deleted the programs I had to redo it, and so on. I made the folders I wanted shared, through the share menu when you right click on them, and they show up on the other computer, but I can't access them. It says I don't have access rights and to contact the administrator, but IM the administrator.
So, what do I do?

Disable all firewall on both the computers ....
Try to ping one computer to another ... see if it works ....
Also you can try this link ..... useful for enabling the sharing of files in a network ...

Sharing network problem - again

Hi, i hoped to avoid posting this problem, but i just can't get internet sharing working!
My setup is this: I have a PC connected directly to a adsl-modem via a netcard, and via a second netcard (and a crossed cable) i have a second PC connected to the first, both are running Archlinux, the first is up to date, but the second is 0.6 (since i can't update...).
The 2 PC's have no problems communicating, ping and ssh is working perfectly both ways.
To share the connection, i have this in the rc.conf:
The one connected to the modem:
lo="lo 127.0.0.1"
eth0="dhcp"
eth1="eth1 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES="lo eth0 eth1"
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
The one needing the connection:
lo="lo 127.0.0.1"
eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255"
#eth0="dhcp"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
And i have this "firewall" installed on the one connected to the internet:
#!/bin/sh
# rc.firewall-2.4
FWVER=0.75
# Initial SIMPLE IP Masquerade test for 2.4.x kernels
# using IPTABLES.
# Once IP Masquerading has been tested, with this simple
# ruleset, it is highly recommended to use a stronger
# IPTABLES ruleset either given later in this HOWTO or
# from another reputable resource.
# Log:
# 0.75 - Added more kernel modules to the comments section
# 0.74 - the ruleset now uses modprobe vs. insmod
# 0.73 - REJECT is not a legal policy yet; back to DROP
# 0.72 - Changed the default block behavior to REJECT not DROP
# 0.71 - Added clarification that PPPoE users need to use
# "ppp0" instead of "eth0" for their external interface
# 0.70 - Added commented option for IRC nat module
# - Added additional use of environment variables
# - Added additional formatting
# 0.63 - Added support for the IRC IPTABLES module
# 0.62 - Fixed a typo on the MASQ enable line that used eth0
# instead of $EXTIF
# 0.61 - Changed the firewall to use variables for the internal
# and external interfaces.
# 0.60 - 0.50 had a mistake where the ruleset had a rule to DROP
# all forwarded packets but it didn't have a rule to ACCEPT
# any packets to be forwarded either
# - Load the ip_nat_ftp and ip_conntrack_ftp modules by default
# 0.50 - Initial draft
echo -e "nnLoading simple rc.firewall version $FWVER..n"
# The location of the iptables and kernel module programs
# If your Linux distribution came with a copy of iptables,
# most likely all the programs will be located in /sbin. If
# you manually compiled iptables, the default location will
# be in /usr/local/sbin
# ** Please use the "whereis iptables" command to figure out
# ** where your copy is and change the path below to reflect
# ** your setup
#IPTABLES=/sbin/iptables
IPTABLES=/usr/sbin/iptables
DEPMOD=/sbin/depmod
MODPROBE=/sbin/modprobe
#Setting the EXTERNAL and INTERNAL interfaces for the network
# Each IP Masquerade network needs to have at least one
# external and one internal network. The external network
# is where the natting will occur and the internal network
# should preferably be addressed with a RFC1918 private address
# scheme.
# For this example, "eth0" is external and "eth1" is internal"
# NOTE: If this doesnt EXACTLY fit your configuration, you must
# change the EXTIF or INTIF variables above. For example:
# If you are a PPPoE or analog modem user:
# EXTIF="ppp0"
EXTIF="eth0"
INTIF="eth1"
echo " External Interface: $EXTIF"
echo " Internal Interface: $INTIF"
#======================================================================
#== No editing beyond this line is required for initial MASQ testing ==
echo -en " loading modules: "
# Need to verify that all modules have all required dependencies
echo " - Verifying that all kernel modules are ok"
$DEPMOD -a
# With the new IPTABLES code, the core MASQ functionality is now either
# modular or compiled into the kernel. This HOWTO shows ALL IPTABLES
# options as MODULES. If your kernel is compiled correctly, there is
# NO need to load the kernel modules manually.
# NOTE: The following items are listed ONLY for informational reasons.
# There is no reason to manual load these modules unless your
# kernel is either mis-configured or you intentionally disabled
# the kernel module autoloader.
# Upon the commands of starting up IP Masq on the server, the
# following kernel modules will be automatically loaded:
# NOTE: Only load the IP MASQ modules you need. All current IP MASQ
# modules are shown below but are commented out from loading.
# ===============================================================
echo "----------------------------------------------------------------------"
#Load the main body of the IPTABLES module - "iptable"
# - Loaded automatically when the "iptables" command is invoked
# - Loaded manually to clean up kernel auto-loading timing issues
echo -en "ip_tables, "
$MODPROBE ip_tables
#Load the IPTABLES filtering module - "iptable_filter"
# - Loaded automatically when filter policies are activated
#Load the stateful connection tracking framework - "ip_conntrack"
# The conntrack module in itself does nothing without other specific
# conntrack modules being loaded afterwards such as the "ip_conntrack_ftp"
# module
# - This module is loaded automatically when MASQ functionality is
# enabled
# - Loaded manually to clean up kernel auto-loading timing issues
echo -en "ip_conntrack, "
$MODPROBE ip_conntrack
#Load the FTP tracking mechanism for full FTP tracking
# Enabled by default -- insert a "#" on the next line to deactivate
echo -en "ip_conntrack_ftp, "
$MODPROBE ip_conntrack_ftp
#Load the IRC tracking mechanism for full IRC tracking
# Enabled by default -- insert a "#" on the next line to deactivate
echo -en "ip_conntrack_irc, "
$MODPROBE ip_conntrack_irc
#Load the general IPTABLES NAT code - "iptable_nat"
# - Loaded automatically when MASQ functionality is turned on
# - Loaded manually to clean up kernel auto-loading timing issues
echo -en "iptable_nat, "
$MODPROBE iptable_nat
#Loads the FTP NAT functionality into the core IPTABLES code
# Required to support non-PASV FTP.
# Enabled by default -- insert a "#" on the next line to deactivate
echo -en "ip_nat_ftp, "
$MODPROBE ip_nat_ftp
#Loads the IRC NAT functionality into the core IPTABLES code
# Required to support NAT of IRC DCC requests
# Disabled by default -- remove the "#" on the next line to activate
#echo -e "ip_nat_irc"
#$MODPROBE ip_nat_irc
echo "----------------------------------------------------------------------"
# Just to be complete, here is a partial list of some of the other
# IPTABLES kernel modules and their function. Please note that most
# of these modules (the ipt ones) are automatically loaded by the
# master kernel module for proper operation and don't need to be
# manually loaded.
# ip_nat_snmp_basic - this module allows for proper NATing of some
# SNMP traffic
# iptable_mangle - this target allows for packets to be
# manipulated for things like the TCPMSS
# option, etc.
# ipt_mark - this target marks a given packet for future action.
# This automatically loads the ipt_MARK module
# ipt_tcpmss - this target allows to manipulate the TCP MSS
# option for braindead remote firewalls.
# This automatically loads the ipt_TCPMSS module
# ipt_limit - this target allows for packets to be limited to
# to many hits per sec/min/hr
# ipt_multiport - this match allows for targets within a range
# of port numbers vs. listing each port individually
# ipt_state - this match allows to catch packets with various
# IP and TCP flags set/unset
# ipt_unclean - this match allows to catch packets that have invalid
# IP/TCP flags set
# iptable_filter - this module allows for packets to be DROPped,
# REJECTed, or LOGged. This module automatically
# loads the following modules:
# ipt_LOG - this target allows for packets to be
# logged
# ipt_REJECT - this target DROPs the packet and returns
# a configurable ICMP packet back to the
# sender.
echo -e " Done loading modules.n"
#CRITICAL: Enable IP forwarding since it is disabled by default since
# Redhat Users: you may try changing the options in
# /etc/sysconfig/network from:
# FORWARD_IPV4=false
# to
# FORWARD_IPV4=true
echo " Enabling forwarding.."
echo "1" > /proc/sys/net/ipv4/ip_forward
# Dynamic IP users:
# If you get your IP address dynamically from SLIP, PPP, or DHCP,
# enable this following option. This enables dynamic-address hacking
# which makes the life with Diald and similar programs much easier.
echo " Enabling DynamicAddr.."
echo "1" > /proc/sys/net/ipv4/ip_dynaddr
# Enable simple IP forwarding and Masquerading
# NOTE: In IPTABLES speak, IP Masquerading is a form of SourceNAT or SNAT.
# NOTE #2: The following is an example for an internal LAN address in the
# 192.168.0.x network with a 255.255.255.0 or a "24" bit subnet mask
# connecting to the Internet on external interface "eth0". This
# example will MASQ internal traffic out to the Internet but not
# allow non-initiated traffic into your internal network.
# ** Please change the above network numbers, subnet mask, and your
# *** Internet connection interface name to match your setup
#Clearing any previous configuration
# Unless specified, the defaults for INPUT and OUTPUT is ACCEPT
# The default for FORWARD is DROP (REJECT is not a valid policy)
echo " Clearing any existing rules and setting default policy.."
$IPTABLES -P INPUT ACCEPT
$IPTABLES -F INPUT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -F OUTPUT
$IPTABLES -P FORWARD DROP
$IPTABLES -F FORWARD
$IPTABLES -t nat -F
echo " FWD: Allow all connections OUT and only existing and related ones IN"
$IPTABLES -A FORWARD -i $EXTIF -o $INTIF -m state --state ESTABLISHED,RELATED -j ACCEPT
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT
$IPTABLES -A FORWARD -j LOG
echo " Enabling SNAT (MASQUERADE) functionality on $EXTIF"
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE
echo -e "nrc.firewall-2.4 v$FWVER done.n"
And to start it:
#!/bin/sh
# chkconfig: 2345 11 89
# description: Loads the rc.firewall-2.4 ruleset.
# processname: firewall-2.4
# pidfile: /var/run/firewall.pid
# config: /etc/rc.d/rc.firewall-2.4
# probe: true
# v05/24/03
# Part of the copyrighted and trademarked TrinityOS document.
# http://www.ecst.csuchico.edu/~dranch
# Written and Maintained by David A. Ranch
# [email protected]
# Updates
# 05/24/03 - removed a old networking up check that had some
# improper SGML ampersand conversions.
# Source function library.
. /etc/rc.d/functions
# Check that networking is up.
[ "XXXX${NETWORKING}" = "XXXXno" ] && exit 0
[ -x /sbin/ifconfig ] || exit 0
# The location of various iptables and other shell programs
# If your Linux distribution came with a copy of iptables, most
# likely it is located in /sbin. If you manually compiled
# iptables, the default location is in /usr/local/sbin
# ** Please use the "whereis iptables" command to figure out
# ** where your copy is and change the path below to reflect
# ** your setup
IPTABLES=/usr/sbin/iptables
# See how we were called.
case "$1" in
start)
/etc/rc.firewall-2.4
stop)
echo -e "nFlushing firewall and setting default policies to DROPn"
$IPTABLES -P INPUT DROP
$IPTABLES -F INPUT
$IPTABLES -P OUTPUT DROP
$IPTABLES -F OUTPUT
$IPTABLES -P FORWARD DROP
$IPTABLES -F FORWARD
$IPTABLES -F -t nat
# Delete all User-specified chains
$IPTABLES -X
# Reset all IPTABLES counters
$IPTABLES -Z
restart)
$0 stop
$0 start
status)
$IPTABLES -L
mlist)
cat /proc/net/ip_conntrack
echo "Usage: firewall-2.4 {start|stop|status|mlist}"
exit 1
esac
exit 0
But it just won't work! If you can spot any problems please let me know!
UPDATE:
Just talked to my ISP, and they tell me that my IP-adress is locked to one PC. Could this be the problem? or does the forwarding handles this as well?

Hey tgc, thank you for posting your problem so generously explained!
I had no idea of how to do it, and I only had to change a small obvious typo to make it work. At least I suppose the typo is the reason for your sharing not to work....
Lets see...did you change the
eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.0.255"
to
eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255"
just now? I'm sure I had to change that, but I have a strange memory
So, the way the configuraton looks now, works perfectly for sharing my isdn connection with my laptop over wlan.
Desktop: isdn, eth0 -> wireless router / hub
Laptop: wlan0
So, what I'm saying anyway, is that your configuration works for me Thanks!

Personal File Sharing & Network in the Sidebar

I have had the same symptoms as other posts; but the real answer was not given, YET.
If you use the Network icon in the Sidebar, and you move between networks, Where or How do you Refresh the Finder? Rebooting or Shutdown is not the answer. Windows Networking on PCs allows for Refreshing, why not OS X?
My Senario: iMac G5 1.9 & iBook G4 1.33, both 10.4.10, no broadband, I share via Ad-Hoc. Both connect and IP given 169.x.x.x.
iBook will see iMac via Finder>Network Sidebar after about 5 seconds. iMac will not see iBook via Finder>Network Sidebar. Both have Network and Sharing set the same.
Using CMD+k, entering IP will bring up Authenticate window, which is fine, but DHCP is on, and the IP changes each time. Want Finder>Network to find the computer for me.
Using ShiftCMDK, on iBook, sometimes opens the Network Finder window, most times it never opens. (when at home)
iBook goes to hot-spots and when I come home, I want to off-load files to the iMac. The Network Sidebar remembers the last Network you were connected to with a list of all the computers you could connect to; I sleep the iBook.
Is there a terminal command to Refresh the Network without rebooting?
Big tip: I found an old Apple Article which states;
"The Local Hostname for your computer is an alternative to the network address. It is followed by ".local". Users on the same network subnet as your computer can use the Local Hostname name to access certain resources on your computer, such as your personal website. If you work in a large network environment, users on a different IP subnet cannot use the Local Hostname name of your computer."
So, if you use CMD+k while on your LAN and use "nnn.local" for the IP, you get the Authenticate window. This works fine, both machines can do this all day; But, still does not answer nor solve the question...
How do you Refresh Finder>Network ?!?!?
iMac G5 17-inch 1.9GHz SuperDrive (iSight) Mac OS X (10.4.10) 1.5GB RAM

Is there a terminal command to Refresh the Network without rebooting?
Couple of things that Might work...
sudo ipconfig set en0 BOOTP;sudo ipconfig set en0 DHCP
sudo ifocnfig en1 down
sudo ifconfig en1 up
(use en0 for Ethernet, en1 for Airport, etc.)
But making a New Location for each place would probably work best/easiest. You can tailor each location to it's needs.

File sharing: Win7-Win8 vs Win8-Win8

1st... I have searched for help at Microsoft and, other than several people discussing this in the Microsoft forums, I do not find any actual answers
My wife's new computer runs Win8 while I am still on Win7 (both 64bit Pro versions, with all updates from Microsoft)
I am "in charge" of making backup copies of her important files, which I (try to) do from my computer via setting her folders up with File Sharing
The problem is that "some" of her sub-folders in My Documents do not update when she creates a new file (maybe all sub-folders, I have not looked at every one)
So, my question... is there anyone here with two Win8 computers connected through a router (mine is DSL modem with 4 Ethernet plugs) where File Sharing settings work properly?
This is enough of an annoyance that I am considering upgrading my computer to Win8, even though my current Win7 works perfectly in every other way
ADDED
Also, I have always performed a clean install in the past... But, to save time and keep all my settings... how is the Win8 upgrade over Win7 process?

Went to http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US and entered various search terms
Creating and joining a homegroup is explained, and is SUPPOSED to be easy... except when it doesn't work right... part of which is conflicting information on creating the homegroup in W8 and then joining from W7... or the reverse
I think I'm going to have to wait for a day when my wife is going to be out running errands, so I can make a backup http://www.terabyteunlimited.com/image-for-linux.htm of both of our boot drives, to be able to restore if I can't get a W8-to-W7 homegroup working properly
Then, last resort, is running the W8 upgrade on my computer so we are both using the save OS
Grin... all of this so I don't have to walk across the office and copy from a 2nd level My Documents--Plans folder to a 1st level folder to make copies of her files

Problem using File sharing in a small office network

I have a problem using File sharing on an Imac and Macbook Pro.
My office has a small network running Windows Small office file server 2003. I have one Windows 2000 PC connected to it and 3 Macs, an 2.4 gHz Intel iMac running Leopard 10.5.6 , a MBP running the same and a Mac Mini running 10.5.
From the Finder Shared window of the Mac Mini, I can see all the computers on the network. It also used to be the case for the iMac, but the MBP could never see the Windows PC’s, not the server or the Win2000. This wasn’t a big problem as I was communicating between the Macs and using the shared printer on the iMac.
On Monday Jan 19 the iMac was suddenly unavailable to the other 2 Macs. It was working normally on the Friday. The iMac can access the Mac Mini and copy files to it. The Mac Mini can see the iMac but cannot access it. Even trying to connect as, ends in a failed connection. I have tried rebooting, turning File sharing off and then on again to no avail.
The iMac now also cannot see the Windows PC’s which it previously could.
To get files from the MBP for printing, I now copy it to the Mac Mini and acces the folder from the iMac, a very tedious procedure. I don’t know why this happened and am scared that the Mac Mini is going to do the same thing.
All three computers are also running VMware 2.0 with Windows XP pro, and from VMware the server is visible on all the computers.
Any help will be much appreciated, I live in a small town in South Africa and the local computer suppliers have no knowledge of the Macs.
I think that the problem with the iMac may have started after a software upgrade to 10.5.6 but I am not entirely sure.
Thank you
ajdk

Well, you're current method sounds pretty good. But if you want to user a file server, hey go ahead.
What you want to do when you centralize project files is to keep track of which one is the newest and becareful not to overwrite files with the same name. So you either have to set up individual spaces on the server (separate AFP/FTP folders maybe), or you'll need to run a file checkout service.
The individual space is cheaper, but it's not much of a difference from backing up to the network drive. Since you have Gigabit connections, you might even opt to save ALL the user files on the server instead of just the project files.
If you want to run a file checkout service, there's two approaches. You can run a service that can host any kind of file, or you can run a version control system for each kind of application (Photoshop, Word, etc.). Please notice, that as you read further and further along, the methods become more and more expensive and complicated. Once you get to this point, it will be necessary to purchase or build software in addition to the Mac OS X Server package.

File sharing across a network --- Mac (Leopard) and PCs (Vista) -- problems

Been trying to setup file sharing so that I can access an iMac from a Vista PC. Followed various help threads, and have a specific question as relates to setting the file sharing preferences. From system preferences/sharing, have checked "File Sharing", and the shared folders displayed are the default public ones for the two users of the iMac. That is what I want. I next click on the options button in the same sharing window, where "Share files and folders using AFP" is already turned on (checked). From the data I have read, I next try to set up sharing using SMB, checking on that option (cause I think I must do that - from what I've read).
This is where I run into problems. If I just check for share files and folders using SMB, and don't check off on the individual user accounts, when I try to access the iMac from the Vista PC, I get a login dialog box when I click on the iMac in my network screen. Not sure what to do with that ... _as I only want guest access to the public folders on the iMac_. If, however, in setting up SMB I check on the individual user accounts (and provide the requested passwords), then when I access the iMac from the Vista PC, I don't have to login to the iMac at all .... but all folders/all iMac hard drive data is now available/editable to me. This is not what I want. Only want network access to the iMac public folders. But as I noted earlier, if I set up SMB without checking off on the user account names, then I am presented with a login box when I click on the iMac icon on the Vista PC.
Have read numerous articles on this ... and think I am close. So ... bottom line ... want iMac access from Vista PCs but only want access to the iMac public folders. Don't want access to the entire iMac hard drive.
Any thoughts/suggestions? Thanks.

Some additional insight to share. Some successes, but still some questions.
Was reading around the web on this topic and found something that indicated that I should create a new, non-admin account on the iMac and make that the user that is shared. The other two users that I was attempting to share the public folder were both admin users, and this may account for showing all of the hard drive when I accessed the iMac from the Vista PC.
So I created this new "standard" user account, and share that public folder, and it all works. Now here is the still questionable. From one vista PC, when I click on the iMac I get a login prompt. At that point I can log into the iMac or just access the iMac via guest access. Both work.
But from a different Vista PC, clicking on the iMac does not prompt a login shell to appear. I just walk into the iMac shared folder. Do not understand this behavior. Would've expected that any Vista or windows PC would get a login shell when trying to access the iMac. That is not the case. Any thoughts why the 2 Vista PCs behave differently?

Network problem sharing file with windows 2k pc

I just recieved my macbook a few days ago, and I am new mac user. I tried to set up a network between my macbook and my old win2k pc. I have been trying for many hours with no result. I have enabled window sharing, and personal file sharing, matching the workgroup name. For some reason, i still cannot see my pc under NETWORK.
I have been surfing for previous post relate to this topic, and tried many different solution, still doesn't work.
Anyone can teach me a proper procedure for setting up this?
many thanks
franki

Hi franki, I'm glad those web sites were useful.
Unfortunately I can't advise about your remaining problem because I don't have a suitable Windows computer to try things out on. Maybe somebody else here can.
I'd suggest you give a few more details about exactly how far you get and at which point things get stuck.
Also, if nobody on this board can help then you could try another one. There are several boards here related to networking, of which the Tiger Forums Getting Online & Networking one seems to be the most lively.
MacBook (OS 10.4.8) iMac G4 (OS 10.3.9)

File sharing network problem

Similar Messages

Maybe you are looking for