I am trying to integrate QNX 4.25 into a Microsoft Windows network.
Can anyone offer any help?
All comments, and suggestion welcomed and appreciated.
–Corey
Corey Muprhy <cmu7999321@charter.net> wrote:
I am trying to integrate QNX 4.25 into a Microsoft Windows network.
Can anyone offer any help?
All comments, and suggestion welcomed and appreciated.
Integrate how? If you’re a tcp/ip only based network, then it’s pretty
straight forward. If you need to access shares etc then you should look
at the Samba port for QNX. Look at smbd in the docs and smbclient
-Adam
Previously, Operating System for Tech Supp wrote in qdn.public.qnx4:
Integrate how? If you’re a tcp/ip only based network, then it’s pretty
straight forward. If you need to access shares etc then you should look
at the Samba port for QNX. Look at smbd in the docs and smbclient
An important note. I believe that both Samba and SMB use TCP/IP.
This means that to access Windows Hard disks, you have to bind
their access to TCP/IP. This is very dangerous if your system
is on the Internet.
Mitchell Schoenbrun --------- maschoen@pobox.com
Mitchell Schoenbrun <maschoen@pobox.com> wrote:
Previously, Operating System for Tech Supp wrote in qdn.public.qnx4:
An important note. I believe that both Samba and SMB use TCP/IP.
This means that to access Windows Hard disks, you have to bind
their access to TCP/IP. This is very dangerous if your system
is on the Internet.
As part of the NetBIOS name resolution, even MS-Clients use UDP unicast when
a WINS server is being used, and UDP broadcast without WINS. Also, it would be
foolish to put any server (MS-WinNT etc) that exported shares directly on the
“internet”. Basic network security still must be observed regardless of your
SMB implementation.
-Adam
Previously, Operating System for Tech Supp wrote in qdn.public.qnx4:
Also, it would be
foolish to put any server (MS-WinNT etc) that exported shares directly on the
“internet”.
If the protocol is not TCP/IP it won’t make it past the first router.
\
Mitchell Schoenbrun --------- maschoen@pobox.com
Mitchell Schoenbrun <maschoen@pobox.com> wrote:
Previously, Operating System for Tech Supp wrote in qdn.public.qnx4:
Also, it would be
foolish to put any server (MS-WinNT etc) that exported shares directly on the
“internet”.If the protocol is not TCP/IP it won’t make it past the first router.
Correct, but the NetBIOS (and NetBEUI) protocols are non-routable.
My point was that you shouldn’t export shares (SMB, NFS, etc) on an interface that
is connected to a unknown network (ie. Internet) if you want to have any kind of
security, regardless of the protocol.
-Adam
I thought that that was what I was saying, although a little more
specifically. The problem occurs when you want Samba or SMB,
but you are connected to the Internet. Obviously a firewall
is needed in that case.
Previously, Operating System for Tech Supp wrote in qdn.public.qnx4:
My point was that you shouldn’t export shares (SMB, NFS, etc) on an interface that
is connected to a unknown network (ie. Internet) if you want to have any kind of
security, regardless of the protocol.
Mitchell Schoenbrun --------- maschoen@pobox.com
Mitchell Schoenbrun <maschoen@pobox.com> wrote:
I thought that that was what I was saying, although a little more
specifically. The problem occurs when you want Samba or SMB,
but you are connected to the Internet. Obviously a firewall
is needed in that case.
Ok - sorry about that. Just making sure that I was being clear
-Adam
I think the salient point is that Samba/QNX/Linux/what-have-you aside,
most (probably greater than 90%) of completely native Windows networks
have their services bound to TCP/IP anyway. So the security issues have
little or nothing to do with adding Samba to the mix.
-----Original Message-----
From: Mitchell Schoenbrun [mailto:maschoen@pobox.com]
Posted At: Monday, October 15, 2001 6:57 PM
Posted To: qnx4
Conversation: Integration to a Microsoft network
Subject: Re: Integration to a Microsoft network
I thought that that was what I was saying, although a little more
specifically. The problem occurs when you want Samba or SMB,
but you are connected to the Internet. Obviously a firewall
is needed in that case.
Previously, Operating System for Tech Supp wrote in qdn.public.qnx4:
My point was that you shouldn’t export shares (SMB, NFS, etc) on an
interface that
is connected to a unknown network (ie. Internet) if you want to have
any kind of
security, regardless of the protocol.
Mitchell Schoenbrun --------- maschoen@pobox.com
Previously, Rennie Allen wrote in qdn.public.qnx4:
I think the salient point is that Samba/QNX/Linux/what-have-you aside,
most (probably greater than 90%) of completely native Windows networks
have their services bound to TCP/IP anyway. So the security issues have
little or nothing to do with adding Samba to the mix.
Well I’m talking from my own experience in which adding
Samba did change things. You can BIND file and printer
sharing to Netbui between Win/9x machines. It works just
fine without having a security problem if you are on the
Internet because Netbui is not IP compatible. If you try to
add Samba to this mix you need TCP/IP and therefore you do
have a security problem. I discovered this, to my horror,
late in the game by going to http://www.grc.com and checking
out the “Sheilds UP” feature. I highly recommend this site
to anyone who has a Windows machine on the internet, either
permanently or just via dial up.
–
Mitchell Schoenbrun --------- maschoen@pobox.com