i set up a linux ip masquerading which is causing application problems in windows for client machines behind the firewall. For example when a user uses "Homesite" to access a file accross the firewall on a server, problems arise(i.e. The file wont open/save properly or wil get an I/O error or it will say "read-only file"). Before i set up the masqu., these problems never happened. Furthermore, these problems only happen sometimes. Other times the users will be able to open/save a document without problem.

I had problems with users coming up with similar errors using Homesite.

I very much doubt that masquerading is your problem. Masq won't stop your files from being saved - if you can see them then it's working.

I would direct you to look at the location of the files. Most often the 'can't save this file' problem in Homesite is because the file (on the webserver, file server or what have you) doesn't have the correct permissions.

If your files reside on a *nix share, ensure that your users are listed as either the owner, or member of the group who're allowed permission. Or that they're world writable (not such a good plan, depending on what/where they are).

Slick.

thanks for the reply

permissions is not the problem. like i said, this wasnt happening until i started using the firewall(ip masq). I dont beleive its a server or disk problem, rather a network problem. the server is microsoft.
The same thing happens when I, from within photoshop, open an img file that resides on the server. It comes up as error. Even when i am just using windows desktop(My Network Places) to browse folders on the server I have problems.

Im 99.9% sure it has something to do with the linux firewall (ip masq) i setup.

thanks again

Oky...

Let's see.. How're you accessing the files on your Windows Server?

Are you using samba on your linux box at all. If so, I assume it worked fine pre-masq.

Are you transporting netbios traffic across your masq firewall?

Is your linux box trying to be an authenticating 'windows' box?

Um.. finally, are you and your windows server on different subnets, and why are you masq'ing now, when it worked good before?

Thoughts behind questions :

Samba shares/permission maps problems.
Netbios traffic across firewall might be subject to timeouts(? - I'd need to research this)
Conflicting browser masters could cause dropouts of shares advertised on network.
Curious.

Slick.

this is how we are setup:

1.we dont need samba because it is a 100% microsoft environment . The only non-microsoft is the linux box itself which is acting as the router(ip masqu.).

2. the linux box (RH) is just a router using iptables the script is:
**************************
iptables --table nat --append POSTROUTING --out-interface eth0 -j MASQUERADE
iptables --append FORWARD --in-interface eth1 -j ACCEPT
echo 1 > /proc/sys/net/ipv4/ip_forward
**************************

to internet
|
hardware router
(205.2.2.0-205.2.2.255)
|
|
switch
| |
| |
| |
205.2.2.10 ------
linux box |
ip masq server
(192.168.1.1) 205.2.2.5
|
to internal net

the diagram messed up, here it is again:
**********************

internet
|
hardware router 205.2.2.1
|
switch------------------------- server 205.2.2.2
|
eth0 205.2.2.10
linux box
eth1 192.....
|
internal net

anyone??? this problem is really causing problems and i need advice ASAP!!