OS/2, eCS & ArcaOS - Technical > Networking

OS/2, Realtek and NIC drivers

<< < (5/7) > >>

Ben:
OK.

Two things of note.

ARP -a or netstat -arp in the above posting is reporting the hardware address of a NIC on another machine. This other machine is connected to this one. But there is nothing else given by ARP -a or netstat -arp. I have no idea why this is so, but I'm sure that someone in the OS/2 community does.

Secondly, W7 was able to successfully produce my Adapter Address.

I entered it into the Network Adapter Address entry field for the Mensys RTL driver, (via "Adapters and Protocols"), and rebooted. This time the TCP/IP works... but the Netbios still does not.

Thanks, Neil, it was a good idea, but has not been effective. However, the Physical Address of my onboard NIC is now properly displayed in "netstat -n"... which is something.

Now I have to find that GenMAC RTL driver and see if that works.


Addendum:

But before I do that, there is one more thing of note:

When I first tried the onboard NIC using the rtgnda13 driver that was already installed, (I moved my hardrive from my previous machine to this one), Netbios did not work.

However, when I disabled the onboard NIC and installed my previous NIC in a PCI slot and rebooted, everything worked fine. But I needed that NIC for another machine. I reactivated the onboard NIC and installed the Mensys RTL driver.

Since then, Netbios will not work with either of these NICs; I keep getting that Mugwepop.exe popup when I try to logon the network.

I suspect that installing the Mensys driver altered something else that is not being updated... what that can be I yet, have no idea; time will tell.


Doug Bissett:

--- Quote ---Note that there seems to be a digit missing; a space between the first zero and the first colon.
--- End quote ---
That seems to be a cosmetic thing. I see the same.


--- Quote ---It only accepted 0018e7183689... which as I said, doesn't work.
--- End quote ---
I haven't needed that with any of my Realtek NICS, using the Multimac driver. When I was using RTGNDA, I needed to modify the rtgnda.nif file with this section, at the end:

--- Code: ---[NETADDRESS]
tag = NETADDRESS
display = "Network adapter address"
type = hexstring
strlength = 12
default="3c970e67241b"
optional = yes
editable = yes
help = "NETADDRESS alternates the MAC address of the adapter
with the one fixed in the hardware(in the EEPROM)."

--- End code ---
3c970e67241b is the MAC address of the Realtek NIC. Perhaps it needs the quotes.


--- Quote ---WRT the "NAPS Tool" I am assuming that you mean the little popup window that prompts the user to select from a choice of available LANs; Lan0 or Lan1, etc.
--- End quote ---

No. It is a replacement for the Adapters and Protocols configuration program (AKA MPTS). The fixed one is working well, for me.


--- Quote ---Since then, Netbios will not work with either of these NICs; I keep getting that Mugwepop.exe popup when I try to logon the network.
--- End quote ---
Interesting. Is there a program by that name somewhere on your machine? I find no such thing on my systems.

It appears that you have now isolated the problem to NETBIOS, but it would be good for somebody else to verify that. I will try to find the time to install NETBIOS, on two machines using the Multimac Realtek driver, to see if it will work, or not. If that fails, you have three options: 1) report it properly. 2) use a different NIC, 3) Change to NETBIOS over TCPIP. If I can make it fail, I will report it, but a second report would help to get attention. If it doesn't fail, you need to look elsewhere for your problem. A new install would probably help in that case, but I have a bit of work to do to do a test.

Ben:
C:/MUGLIB/MUGWEPOP.EXE 3-23-04  10:56a          7,365

It has to do with the Netbios logon. It is in the same folder where Mugwepop.exe resides.

You probably do not have it because you have removed it or have not installed it, instead choosing to use SAMBA. And if I knew that the OS/2 handlers of  SAMBA had solved the EA problems, (particularly WRT PMVIEW and images), I'd give it another go, because it does solve a lot of problems that exist with OS/2 LAN Services... it was just that for me the problems with SAMBA were worse than the problems that it solved.

As I said before, the last time I communicated with them, they had done nothing to address those issues and had no intentions of doing so. That was a few years ago... maybe I'll send them another E-mail.

But, WRT Mugwepop.exe, this program strikes a weak bell in my memories from back in a time period when I knew plenty about all things networking WRT OS/2.

The problem with becoming proficient with something is that based upon your skill/knowledge you can put together something really good! Then you do not have to look at it again for ten years... and by then you have forgotten large chunks of it from a complete lack of use.

The only solution then is;

* Go through the frustration of relearning it in long cycles.
* Get someone else to do it or
* Keep it fresh in your mind by wasting time doing the necessaries to keep it up.
Of course, some skills you keep fresh because your way of life keeps it fresh. With everyone, it is a choice. Keep one fresh at the expense of another.

Oh, well. It is just one of the troughs of those long-term cycles reoccurring.

Hmmph! 8|

Anyway. I'll solve it. It is just a question of how much piss and vinegar I have to spit first. 8)


These days I covet every moment of my time and give it up only with a battle. In fact, one of the reasons that I use OS/2 is because ONCE SETUP, it will work very well indeed, with little need for attention... unlike any flavour of Windows or *nix... which require nursemaiding and constant attention if only in the incessant learning of arcane parameters designed to be jampacked full of obscure, completely unintuitive, jargon that is designed to appeal to the the mind of the socially inept, introvert.

Being able to use it or learn to use it, is irrelevant - though clearly it is a personal thing - Why? I simply have more important things to do with my time... though in my youth, I did waste much time there, I have grown. So, now when I have to "waste my time" (re)learning this, it bothers me; I feel like I'm being robbed!

But, like any sh*t job, it is best to just do it and be done with it.

But enough for today. The rest will be handled tomorrow... if I can keep it open that is...

Doug Bissett:

--- Quote ---It appears that you have now isolated the problem to NETBIOS, but it would be good for somebody else to verify that. I will try to find the time to install NETBIOS, on two machines using the Multimac Realtek driver, to see if it will work, or not. If that fails, you have three options: 1) report it properly. 2) use a different NIC, 3) Change to NETBIOS over TCPIP. If I can make it fail, I will report it, but a second report would help to get attention. If it doesn't fail, you need to look elsewhere for your problem. A new install would probably help in that case, but I have a bit of work to do to do a test.
--- End quote ---

Well, that was an interesting exercise. I discovered two things:
1) NETBIOS works fine with the latest Multimac driver for Realtek devices, in either direction.
2) Apparently it is just NETBIOS over TCPIP that does not coexist with SAMBA. NETBIOS seems to be okay with it (which makes sense after thinking about it).

So, it would seem that you have some other problem...

Alex Taylor:
Examine \ibmcom\lantran.log for clues, or better still, post it here.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version