Today I added a VLAN to a physical interface. Before the change, eth1 had the address 194.xxx.xxx.xxx. On this network we had a samba server.
I added two VLANs to the interface: VLAN 99: 194.xxx.xxx.xxx netmask 255.255.255.248 VLAN 100: 192.168.7.1 netmask 255.255.255.0 and changed the physical interface to 192.168.99.1 netmask 255.255.255.0 The firewall is connected to a HP switched and the port on eth1 is connected to is tagged with VLAN 99 and 100. Everyhting worked OK, excapt that Windows clients on a different physical interface (eth2) are not longer able to contact the samba server at 194.xxx.xxx.xxx network. The firewall log shows that the traffic is going through it, but it does not work. I also have a linux server on the eth2 interface, and I have no problem in making a ssh connection from the samba server to the linux server on the eth2 interface. It seems like samba does not like VLANs, but I find that very strange, OR? IIt should not be like this, should it? The setup looks like this: +-- XP client | +-- Windows 2000 client | +-- linux server | | (eth2) +----+ | FW |--- (internet) +----+ | (eth1, VLAN 99) | +-- Samba server | +-- Windows client (from this the samba server is responding) Connections to Internet from the samba server and from the windows machines does also work OK. -- Jørn Dahl-Stamnes ================================================= To set vacation, Out-Of-Office, or away messages, send an email to [EMAIL PROTECTED] in the BODY of the email add: set fw-1-mailinglist nomail ================================================= To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================= If you have any questions on how to change your subscription options, email [EMAIL PROTECTED] =================================================
