[Gllug] Linux -> windows issues

[Chris Bell]

On Sat 11 Jun, Matthew Cooke wrote:
> 
> Adrian McMenamin wrote:
> 
> >On Fri, 2005-06-10 at 23:25 +0100, Matthew Cooke wrote:
> >
> >  
> >
> >>The linux boxes and windows boxes are all on the same switch. MDNS is 
> >>being used for discovery and the linux machines all discover each other. 
> >>the windows machines neither discover each other OR the the linux 
> >>machines. The system is peer-to-peer so there is no client/server in the 
> >>traditional sense.
> >>    
> >>
> >>All the machines can ping each other yes. I don't have much experience 
> >>debugging multicast problems so I don't know if I can test the 
> >>224.0.0.251 multicasting in windows directly.
> >>
> >>Matt.
> >>    
> >>
> >
> >
> >How can they ping each other when they don't know they are there? I
> >assume the first paragraph means the Window boxes cannot see the
> >network.
> >
> >  
> >
> I'm not being very clear am I! I know which machines are on the network 
> and their IP addresses so I can manually ping one from another. I'm 
> trying to use mDNS so they can "auto"discover the other machines this is 
> so that they the software that runs on them can automatically configure 
> the machines to work togethor correctly and dynamically handle machines 
> being added or removed. Traditional networking between all the machines 
> is fine (they can ping each other, access file shares etc,) The only 
> problem I have is that Windows XP machines aren't receiving the 
> zeroconf/rendevous/mdns broadbcast packets/events and I have no idea why 
> - i've tried messing with IGMP registry entries but according to MSDN, 
> XP should be IGMP enabled out of the box. (I believe it's IGMP that 
> allows the machines to handle ndns).
> 
> I thought maybe someone might know some other way to test 
> zeroconf/rendezvous/mDNS on windows or have got it working.
> 
> Matt.

   I may be wrong, but AFAIK setting the IP address on each individual
machine does not automatically propagate on to the others. Your
"traditional" networking is just SMB networking which uses the interface MAC
addresses, not TCP/IP.
   You need to run a DHCP server to allow automatic TCP/IP allocation, or
have a real DNS server and then specify the numerical IP address of that
server in the TCP/IP configuration of each box. The ideal would be a Linux
box running BIND9 as a DNS server, with each individual box given the IP
address of the server.

-- 
Chris Bell

-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug