I have some problems with mapping drives on a samba server after I added
VLANs to a FW-1 (CheckPoint). The network looks like this:
+-- XP client
|
+-- Windows 2000 client
|
+-- linux server
|
| (eth2)
+----+
| FW |--- (internet)
+----+
| (eth1)
|
+-- Samba server (linux)
|
+-- Windows client (from this the samba server is responding)
All devices are connected to a HP switch. Before I made any changes to the
firewall, it worked OK.
What I did was to say that the network where the samba server is located, is
on a VLAN. The switch was reconfigured. After the changes, I can do a ssh
from the samba server to the linux server on the eth2 interface. I can also
connect a http session from the Windows client on eth1.99 to the linux
server at eth1.
When trying to map a samba drive from the XP client or the Windows 2000
client on the eth1 network to the samba server, does not longer work. I can
map it and it shows up in the disk drive list, but when trying to look at
it using the explorer, the explorer freeze and is not longer responding.
The log in the firewall (which log all traffic) shows nothing wrong.
The windows client on eth1.99 does still work as before.
It seems like Samba server does not like VLAN, which is something I find
VERY strange. After all, the machines should give a damn about VLANS, since
it does not know about it.
Comments, hints, solutions, explanations?
--
Jørn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/index.php