But the win wks on the other subnet is configured to use my SAMBASERVER as its WINS SERVER, and it is configured using the IP Adress of the SAMBASERVER and not the name. Shouldn't this do the trick? win wks is on a wireless subnet and hence runs at 11 MBPS, while the SAMBASERVER is on a wired subnet. I read somewhere that windows does some kind of "optimization" with slow networks. Is it possible that this is a result of that? or am I way of the target here? - Murali -----Original Message----- From: mike@bizittech.com [mailto:mike@bizittech.com] Sent: Wednesday, May 28, 2003 6:39 AM To: ganapathy murali krishnan Subject: Re: [Samba] Cross Subnet WINS? If you want it to work the win wks must be able to resolve the name SAMBASERVER . Unfortunateley the only way it can is through wins . So you need to add a dns entry to your privtate dns with a hostname SAMBASERVER.yourdomain.com and use that name for dns server or just enter the ip address . Thanks ----- Original Message ----- From: "ganapathy murali krishnan" <gmurali@cs.uchicago.edu> To: <samba@lists.samba.org> Sent: Tuesday, May 27, 2003 7:58 PM Subject: [Samba] Cross Subnet WINS?> > I have a question about WINS across subnets. I am > *not* interested in cross subnet browsing. > > SAMBASERVER is my PDC as well as WINS. > I run "net view \\CLIENT" on a windows machine > A which is on the same subnet as my SAMBASERVER > and everything works fine. > If I run the same command on a windows machine B > on another subnet it does not work. The network > interface on B has been configured to use SAMBASERVER > (rather its IP address) as the WINS server. > > I dont know if this is important. But A is on a wired > network, and B is on a wireless network. > > - Murali > > -- > To unsubscribe from this list go to the following URL and read the > instructions: lists.samba.org/mailman/listinfo/samba >
OK. The problem is solved. The problem was not with samba. The wireless subnet is controlled by a different group of people, and after a few experiments, I found out that all out going traffic to port 139 is dropped. So, I was able to contact my SAMBASERVER on port 22 (ssh) but not on 139. Till I get the firewall opened up, I have asked the user to do all NETBIOS resolutions locally through LMHOSTS. - Murali Murali krishnan Ganapathy wrote:> But the win wks on the other subnet is configured to use my > SAMBASERVER as its WINS SERVER, and it is configured using the > IP Adress of the SAMBASERVER and not the name. Shouldn't this > do the trick? > > win wks is on a wireless subnet and hence runs at 11 MBPS, while > the SAMBASERVER is on a wired subnet. I read somewhere that windows > does some kind of "optimization" with slow networks. Is it possible > that this is a result of that? or am I way of the target here? > > - Murali