-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've got a setup where there's a Samba server, acting as a PDC, with two interfaces - 192.168.1.10 and 192.168.2.10. I've got the following stanza in the smb.conf to have it only listen on the .1 interface: bind interfaces only = true interfaces = 192.168.1.10 127.0.0.1 The setup is working well for most users - they can auth to the PDC, mount shares, and their roaming profile works. However, a few users have XP Pro workstations that are themselves dual-homed. For those users, they can authenticate properly to the PDC, but when it comes time to mount their profile, they get an error about Windows not being able to find their profile, so they have to use a local one. They also can't directly mount any shares on the server with the \\NETBIOS_NAME\ calls. If these users pull their plug on the .2 network, it works fine. So does anyone have any suggestions for things we can do, either on the client, samba, or DHCP end, to work around this problem? Thanks, Wade -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFC3llSo4DwsyRGDscRAmSjAKDjmuGsmKw2jPV7zThXa3uTQb1uYQCgwMiJ MlRSxJiEclSbQraUujerRk0=AjXK -----END PGP SIGNATURE-----
sounds like dns problem, do you have 2 dns entries for the server. each network needs 1 in the dns. if you dont use dns in xp c:\windows\system32\drivers\etc locate hosts edit it and add IP hostname in it. try if this works if it does, you definatly know its resolve problems. Louis>-----Oorspronkelijk bericht----- >Van: samba-bounces+louis=van-belle.nl@lists.samba.org >[mailto:samba-bounces+louis=van-belle.nl@lists.samba.org] >Namens H. Wade Minter >Verzonden: woensdag 20 juli 2005 16:02 >Aan: samba@lists.samba.org >Onderwerp: [Samba] Dual-homed weirdness > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >I've got a setup where there's a Samba server, acting as a PDC, with >two interfaces - 192.168.1.10 and 192.168.2.10. I've got the >following stanza in the smb.conf to have it only listen on the .1 >interface: > >bind interfaces only = true >interfaces = 192.168.1.10 127.0.0.1 > >The setup is working well for most users - they can auth to the PDC, >mount shares, and their roaming profile works. > >However, a few users have XP Pro workstations that are themselves >dual-homed. For those users, they can authenticate properly to the >PDC, but when it comes time to mount their profile, they get an error >about Windows not being able to find their profile, so they have to >use a local one. They also can't directly mount any shares on the >server with the \\NETBIOS_NAME\ calls. > >If these users pull their plug on the .2 network, it works fine. So >does anyone have any suggestions for things we can do, either on the >client, samba, or DHCP end, to work around this problem? > >Thanks, >Wade >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.2.4 (Darwin) > >iD8DBQFC3llSo4DwsyRGDscRAmSjAKDjmuGsmKw2jPV7zThXa3uTQb1uYQCgwMiJ >MlRSxJiEclSbQraUujerRk0>=AjXK >-----END PGP SIGNATURE----- >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/listinfo/samba >
Wade: Have you checked the 'Advanced' settings of your network configuration to ensure that 'Client for Microsoft Networks' uses the desired NIC when performing NETBIOS resolution? It sounds like your XP boxes are defaulting to the 192.168.2.x NIC and eventually timing out. Regards, On Wed, 2005-07-20 at 10:01 -0400, H. Wade Minter wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I've got a setup where there's a Samba server, acting as a PDC, > with > two interfaces - 192.168.1.10 and 192.168.2.10. I've got the > following stanza in the smb.conf to have it only listen on the .1 > interface: > > bind interfaces only = true > interfaces = 192.168.1.10 127.0.0.1 > > The setup is working well for most users - they can auth to the > PDC, > mount shares, and their roaming profile works. > > However, a few users have XP Pro workstations that are themselves > dual-homed. For those users, they can authenticate properly to the > PDC, but when it comes time to mount their profile, they get an > error > about Windows not being able to find their profile, so they have to > use a local one. They also can't directly mount any shares on the > server with the \\NETBIOS_NAME\ calls. > > If these users pull their plug on the .2 network, it works fine. > So > does anyone have any suggestions for things we can do, either on > the > client, samba, or DHCP end, to work around this problem? > > Thanks, > Wade > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (Darwin) > > iD8DBQFC3llSo4DwsyRGDscRAmSjAKDjmuGsmKw2jPV7zThXa3uTQb1uYQCgwMiJ > MlRSxJiEclSbQraUujerRk0= > =AjXK > -----END PGP SIGNATURE----- > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > > -- > This message has been scanned for viruses and > dangerous content and is believed to be clean. >-- Dean Davis,RHCE,MCSE,MCDBA,CCNA,Linux+ Sr. Network Engineer MBG Telecom Software P. 212.822.4429 F. 212.822.4499 W. www.mbg-inc.com GPG/PGP: 1024D/A9C110B4 -- The information in this email (including any attachments) is confidential and may be legally privileged. Access to this e-mail by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it (including any attachments) is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, all attachments, and any copies thereof from your system and destroy any printout thereof. This message has been scanned for viruses and dangerous content and is believed to be clean.