<SNIP> But I'm not routing between the networks. So I'm confused. I simply have a computer that happens to be on two networks. Does that still make it a router? And if so, what is the proper routing configuration to make this work? </SNIP> That depends on whether machines on one network need to see machines on the other. If they do then the machine that straddles the networks has to be a router for the two networks, and incidentally the machines on both networks will need to be able to talk to each other because the communication is in effect a conversation. Do any machines that connect to Samba via SSH need to see or access any other 10. network machines? <SNIP> The sticking point is this. The 10 network on the server is not like DIRECTLY connected to the machine trying to get to the samba share. And there's a little indirection on the SSH side, because we're trying to get to SSH via a virtual server on our firewall (i.e. the firewall says all SSH requests for me get passed onto this internal server). So I'm guess that the fact that it's configured as described above, could contribute to the problem I'm having. I just need to figure out the proper routing configuration to enable both things (Samba over the 10 and SSH over the 192 through the firewall) to work at the same time. </SNIP> So, the Samba server is not on this machine? It's somewhere on the 10. network? That would explain a lot. You need to understand that this server is indeed routing. You then need to setup routing so that it works between the networks. You could put the routes to the two networks in the expert mode in YaST. They will look like... Destination 10.0.0.0 Gateway Something on this network can be the IP of this machine, it should be the IP of a device that knows what to do with packets for unknown networks, like a router or gateway to the internet. Netmask 255.255.0.0 Device Choose the correct one Note that 10. networks are class b so the netmask is usually 255.255.0.0 and 192 networks are class c so the netmask is usually 255.255.255.0. Also make sure that you tick the enable IP forwarding item in the YaST routing module. You will also need to make sure that the machine with the Samba server knows how to get to the router machine (get used to calling it that, that's what it is). You could put a route to the 192 network on this machine with the IP address of the router as the gateway address. Alternatively, if this is correct, you could set the router machine as the gateway address for the Samba server, but it depends if you connect to the internet from the 10 Network through another machine. You could also put the route to the 10. network in the gateway device on the 10. network, if you have access to it, which would be a moer reliable and complete solution as it is easier to setup new devices on the network. Damon