Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

LAN versus PEER

3 views
Skip to first unread message

Lars Erdmann

unread,
Apr 4, 2009, 9:48:46 AM4/4/09
to
Hallo,

recently I set up Netbios via TCP/IP and installed the LAN services. What is
confusing to me is that it somehow has 2 modes of operation:
1.) in a Domain with a dedicated Domain Server
2.) as a Peer

2.) works perfectly well but 1.) does not even though I specified a NetBios
Domain Server. One might say why bother with 1.) when 2.) works ok. This is
true but sometimes I accidentally select to login to a Domain instead of as
a Peer and then the system sits there for ages and the logon never stops
neither with an error message nor with success (at least when this happens
the second time)

Can someone tell me what I have to do to make 1.) work ? By the way: I am
using DHCP on the NIC that is tied to TCP/IP as well as "Netbios via
TCP/IP". DHCP has never timed out so far as I have a DSL Router with DHCP
Server built in that is always powered.

P.S.: I would also like to know about known issues for all of the parameters
you can set for the Netbios protocol: number of GDT entries, size of
datagrams etc. etc. etc.


Lars


Jim Moe

unread,
Apr 5, 2009, 2:27:15 AM4/5/09
to
On 04/04/09 06:48 am, Lars Erdmann wrote:
>
> recently I set up Netbios via TCP/IP and installed the LAN services. What is
> confusing to me is that it somehow has 2 modes of operation:
> 1.) in a Domain with a dedicated Domain Server
> 2.) as a Peer
>
> Can someone tell me what I have to do to make 1.) work ?
>
The LAN server must give you access to its services, i.e., an account.
It may further assign various objects, such as volumes or printers, to
drive letters or lpt ports when you "log on to the network."
The LAN services offer a managed set of services.
PEER is completely anarchic: it is up to all of the individuals to
cooperate to offer and use services on each others computers.

--
jmm (hyphen) list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)

Alex Taylor

unread,
Apr 5, 2009, 9:58:01 AM4/5/09
to
On Sat, 4 Apr 2009 13:48:46 UTC, "Lars Erdmann" <lars.e...@arcor.de> wrote:

> recently I set up Netbios via TCP/IP and installed the LAN services. What
> is confusing to me is that it somehow has 2 modes of operation:
> 1.) in a Domain with a dedicated Domain Server
> 2.) as a Peer

Correct. Peer is useful for quick and simple workstation-to-workstation
connections, or if you don't have a Domain Server on the network.


> 2.) works perfectly well but 1.) does not even though I specified a
> NetBios Domain Server. One might say why bother with 1.) when 2.) works
> ok. This is true but sometimes I accidentally select to login to a Domain
> instead of as a Peer and then the system sits there for ages and the logon
> never stops neither with an error message nor with success (at least when
> this happens the second time)

Well, the obvious question is, do you _have_ a Domain Server on the network?


> Can someone tell me what I have to do to make 1.) work ?

Make sure you're running a LAN domain server (running NetBIOS over TCP/IP)
on the local network. Make sure you specify the name of that domain as
the login domain when you go to log in.

Suitable LAN domain servers include Warp Server, Windows ** Server, and
Samba (at least in certain configurations).

--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00

Please take off hat when replying.

Lars Erdmann

unread,
Apr 5, 2009, 11:34:52 AM4/5/09
to
Alex Taylor schrieb:

> On Sat, 4 Apr 2009 13:48:46 UTC, "Lars Erdmann" <lars.e...@arcor.de> wrote:
>
>> recently I set up Netbios via TCP/IP and installed the LAN services. What
>> is confusing to me is that it somehow has 2 modes of operation:
>> 1.) in a Domain with a dedicated Domain Server
>> 2.) as a Peer
>
> Correct. Peer is useful for quick and simple workstation-to-workstation
> connections, or if you don't have a Domain Server on the network.
>
>
>> 2.) works perfectly well but 1.) does not even though I specified a
>> NetBios Domain Server. One might say why bother with 1.) when 2.) works
>> ok. This is true but sometimes I accidentally select to login to a Domain
>> instead of as a Peer and then the system sits there for ages and the logon
>> never stops neither with an error message nor with success (at least when
>> this happens the second time)
>
> Well, the obvious question is, do you _have_ a Domain Server on the network?

No and that's the point: can I set up a LAN Domain Server with the eCS
1.2 CD-ROM that I have or is additional SW necessary (which obviously I
would not have) ? I thought that it would be sufficient to specify the
IP Address of one of my machines (they are all in the same subnet) to be
the NETBIOS NameServer and NETBIOS Datagram Server in the NETBIOS
protocol configuration but this is a different pair of shoes, is it ?

>
>
>> Can someone tell me what I have to do to make 1.) work ?
>
> Make sure you're running a LAN domain server (running NetBIOS over TCP/IP)
> on the local network. Make sure you specify the name of that domain as
> the login domain when you go to log in.
>
> Suitable LAN domain servers include Warp Server, Windows ** Server, and
> Samba (at least in certain configurations).

Hm that looks like I need a special OS/2 | eCS Version in order to set
up a LAN Server, correct ?

Lars

Lars Erdmann

unread,
Apr 5, 2009, 11:37:07 AM4/5/09
to
Can someone tell me how I can quickly time out the Domain logon dialog ?
Once I have accidentally invoked it, I have to reboot before I can retry
and logon as PEER ...

Lars

Lars Erdmann schrieb:

Lars Erdmann

unread,
Apr 6, 2009, 6:40:37 PM4/6/09
to
Answering my own question:

using
logon.exe /L

instead of:
logon.exe /V:NONE

will logon locally (PEER) and at the same time will gratiously accept a
second,third,... attempt to logon again. "logon.exe /V:NONE" on the
other hand will completely block on any further attempt to logon and you
will be forced to shutdown and restart.

Lars

Lars Erdmann schrieb:

Alex Taylor

unread,
Apr 8, 2009, 7:53:01 AM4/8/09
to
On Sun, 5 Apr 2009 15:34:52 UTC, Lars Erdmann <lars.e...@arcor.de> wrote:

> > Well, the obvious question is, do you _have_ a Domain Server on the
> > network?
>
> No and that's the point: can I set up a LAN Domain Server with the eCS
> 1.2 CD-ROM that I have or is additional SW necessary (which obviously I
> would not have) ?

No and yes.


> I thought that it would be sufficient to specify the
> IP Address of one of my machines (they are all in the same subnet) to be
> the NETBIOS NameServer and NETBIOS Datagram Server in the NETBIOS
> protocol configuration but this is a different pair of shoes, is it ?

Totally different.


> > Suitable LAN domain servers include Warp Server, Windows ** Server, and
> > Samba (at least in certain configurations).
>
> Hm that looks like I need a special OS/2 | eCS Version in order to set
> up a LAN Server, correct ?

Either that, or Samba. You can certainly set one up with Samba, although
it's probably a fair bit of slogging. (Never done it myself, so I can't
be much help there.)

Lars Erdmann

unread,
Apr 24, 2009, 5:53:34 PM4/24/09
to
Answering my one question, these files (that come from IP*8608 fixpak)
are broken:
MUGLRQST.EXE
UPMLAN.DLL

and need to be replaced by those from fixpak IP*8414. See also:
http://www.tavi.co.uk/os2pages/peermcp.html

Once I did that everything is just working fine and I can logon/logoff
any way I like.


Lars


Lars Erdmann schrieb:

Lars Erdmann

unread,
Apr 25, 2009, 4:47:53 AM4/25/09
to
Lars Erdmann schrieb:

> Answering my one question, these files (that come from IP*8608 fixpak)
> are broken:
> MUGLRQST.EXE
> UPMLAN.DLL
>
> and need to be replaced by those from fixpak IP*8414. See also:
> http://www.tavi.co.uk/os2pages/peermcp.html
>
> Once I did that everything is just working fine and I can logon/logoff
> any way I like.

Not true. I had some mix of files. Once I COMPLETELY reapplied IP*8608
it worked without any patch/hack. It's such a mess ...

Lars

0 new messages