| De: |
Jeroen Besse <os2-wireless_users@2rosenthals.com> |
Encabezados Completos
Mensaje no decodificado |
| Enviador: |
os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com> |
| Asunto: |
[OS2Wireless] anyone have GenMac and NETBIOS/TCPIP working? |
| Fecha: |
Wed, 30 Nov 2005 05:39:34 +0100 |
| Para: |
os2-wireless_users@2rosenthals.com |
|
|---|
On 11/30/05, Bob <zejuk9r02@sneakemail.com> wrote:
> ** Reply to message from "Frank Vos frankvos@xs4all.nl" on Wed, 30 Nov 2005
> 01:49:47 +0100 (CET)
>
> > I hope you have it working now (in this case no errors when starting up) with the
> > help of the program or manual changing IBMLAN.INI.
>
> No, it is not working. I thought it might be because I had "dhcpstrt -i lan0
> -d 0" in the setup.cmd so I changed it to "dhcpstrt -i lan0 -d 20" which causes
> a short delay and must be replied to if the wired LAN is not connected but that
> did not make any difference. All this has been tried on the wired LAN
> connection, I have not yet tried the wireless connections using TCPBEUI but
> have little hope it will work either.
>
>
> > To get TCPBEUI working with more than one adapter there is another problem.
> > The problem with TCPBEUI is that the system binds this protocol to the adapter at
> > system startup, so if your WIFI-adapter has no IP address at this moment than it will
> > not have the TCPBEUI protocol.
>
> Since I can not get it working, using TCPBEUI I think I will try and go back to
> NETBIOS and see what I can do. At least it works on the wired LAN connection.
>
> Can anyone tell me why using TCPBEUI is any better than using NETBIOS?
This really depends on your network. TCPBEUI is NETBEUI, packaged
within TCP/IP packets. TCP/IP is routable, while NETBEUI is not. As
soon as you want to connect to a machine that isn't reachable with a
broadcast (for instance because it's behind a router), NETBEUI won't
get you there. However, because of the overhead of TCP/IP, TCPBEUI is
a fraction slower than NETBEUI.
> Is there any way to tell what protocols have been bound to an interface, it
> might make trouble shooting this a little easier?
MPTS should be able to show it. Or, you can have a look at
protocol.ini. The interesting parts from my protocol.ini:
[NETBIOS]
DriverName = netbios$
ADAPTER1 = netbeui$,1
ADAPTER0 = tcpbeui$,0
[netbeui_nif]
DriverName = netbeui$
Bindings = ,E100BEO2_nif
[tcpbeui_nif]
DriverName = tcpbeui$
Bindings = W168CX1014_nif
[tcpip_nif]
DriverName = TCPIP$
Bindings = W168CX1014_nif,E100BEO2_nif
>From this, you can tell that:
- TCP/IP is bound to both adapters
- TCPBEUI is bound to the genmac driver (for an Atheros card) (as number 0)
- NETBEUI is bound to an ethernet driver (as number 1)
Then, over to the interesting part of ibmlan.ini:
[networks]
net1 = TCPBEUI$,0,LM10,34,100,14
net2 = NETBEUI$,1,LM10,34,100,14
net1 uses TCPBEUI, on number 0
net2 uses NETBEUI, on number 1
(further down in ibmlan.ini, I have wrknets and srvnets set to net1,net2)
Btw: with the setup above, Peer works over my genmac driver.
Best regards,
Jeroen Besse
˙-˙-˙-˙-˙-˙-˙-˙-˙-˙-˙
To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).
For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).
This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)
˙-˙-˙-˙-˙-˙-˙-˙-˙-˙-˙
|