Date: Wed, 10 Jun 1998 18:28:34 +0800 (CST) From: Bo Fussing <bmf@gateway.net.hk> To: ICN administrator <root@noc.icn.gov.ru> Cc: isp@FreeBSD.ORG Subject: Re: Sorry, but it concerns NT Message-ID: <Pine.LNX.3.96.980610180310.6143S-100000@gate.gateway.net.hk> In-Reply-To: <357E5369.41C67EA6@noc.icn.gov.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Igor, > Sorry for non-FreeBSD question, but it seems to be ISP-related one. And > i like FreeBSD people. Oh dear me, sounds like you should convince your boss to ditch the NT systems and run FreeBSD - perhaps with SAMBA for NT like file and printer sharing. > I need to connect two LANs (say two class C networks 192.168.1.0 and > 192.168.2.0 ) through corporate IP crowd. There is no problem of > routing, security ,etc. The problem is : those LANs are NT domains (say > Domain1 and Domain2) . And though there are trusted relations between > the domains, and any machine in Domain1 can find and connect to any > machine in Domain2, the former machine cannot get the list of Domain2 in > its neighbourhood and vice versa. You need to use WINS since the standard brain dead way for NT/Windows to discover other hosts on the network is to broadcast over the local subnet. Anything on other subnets is therefore unknown. Use the online documentation provided with NT to work out how this is set up. > And what stroke me most - the Microsoft people in my location can not > resolve the problem, i thought it would be a snap for them. Frightening thing is they call themselves system/network engineers. Regards, Bo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.3.96.980610180310.6143S-100000>