OK, for my @work setting in my .ini file I had originally set a password. I edited my ini file and took that out.... now I can't connect via ftp at all when in @work mode (@home works fine), I re-add the password and I can ftp using the password. The problem is when I try to access the spiffy XML web interface I installed yesterday I get no FTP access (in @work mode.... the @home mode works fine with the web interface and FTP). So my question is how do I go about getting the @work mode to reset itself to deal with no password.

Here is my ini

[synchronise]
seq_num=21
[wendy]
flag_amount=0
[custom]
wendy=
[searches]
amount=0

[options]
Name=Brett's Empeg
[user info]
Email=
Name=Brett

[network]
;@HOME DHCP=0
;@HOME Gateway=192.168.0.1
;@HOME Netmask=255.255.255.0
;@HOME IPAddress=192.168.0.253
;@WORK DHCP=0
;@WORK Gateway=192.190.1.1
;@WORK Netmask=255.255.255.0
;@WORK IPAddress=192.190.1.253

[sense]
muteaction=0
mute=-1
[power]
off_timeout=60000
[display]
caching=0
visual_names=1
[kenwood]
disabled=0
[ramp]
disabled=0
[volumecap]
enabled=0
[hush]
hushpercent=30
[controls]
stalk_side=left
[menu]
quit=0
sort_playlist=1
[tuner]
region=us
[aux]
source=
title=
artist=

Are you sure you need that gateway setting in there?

The gateway should only be filled in if you need to go through that router to get to the empeg (and vice versa). At least I think that's how it works.

Theoretically, the gateway setting is ignored for an address on the local subnet. If both hosts are on the same subnet, it shouldn't matter what it's set to.

However, as Tony says, if you don't need to connect to hosts on a different subnet, leave it blank.

Cool, actually figured out the FTP thing.... I didn't think I needed the gateway, but didn't think it would hurt. After removing the setting all together for @work... snyching... rebooting.. re-adding the setting... it works fine.