"net send" from NT to Windows 98

[flinchlock]

I work from home using W98 SE and RAS (56k). At work, I have an NT domain, which I have an account on. My Win98 PC has "Client for M$ Networks" as the Primary Network Logon, and the same "Workgroup" as the NT domain "ENGINEERING". I logon my PC using the same username and password as the NT domain. My RAS dialup shotcut also uses the same username and password. Also, the RAS shortcut has both WINS addresses the same as used by the NT domain. (The RAS server assigns me a different TCP/IP address each time I call in.)

I can see all the NT controllers/servers/workstations/printers all just fine in my Network Neighborhood. I can connect to all the folder and printer shares with no problems. I can do "net view" and "net view \\workstation" with no problem.

I have have setup c:\windows HOSTS and LMHOSTS files (incase WINS doesn't work). The LMHOSTS file has the PDC with "#PRE #DOM". Also, the WINS server is "#PRE". On the WIN98 PC, "nbtstat -c" shows all LMHOSTS info has loaded into cache.

I can use pcAnywhere to take control of my NT workstation at work. I can ping my Win98 PC from work.

Now for the problem:
====================

I can't get Winpopup (on Win98) and "net send" (on NT) to work. I have tried using "PealPopup" instead of Winpopup on Win98, and also use RealPopup on the NT workstation.

I think the problem has something todo with NBT. Or maybe someway to force a WINS registration of my Win98 PC into the WINS server.

====================

Update: I had to use "arp -s" to associate the TCP/IP address with the physical address (MAC) of the NT workstation at work. Now I can at least send messages to work.

But, still can't send messages/reply from work to home!

[Edited by flinchlock on 10-18-2000 at 05:13 AM]

[GeneC]

It is to my understanding that those programs use NetBIOS to communicate, since you are connecting using a RAS connection (TCP/IP) you might try setting up NetBIOS to run over TCP/IP but I doubt that you'll get it to work that way. NetBIOS is a non routable protocol and if you're passing through any routers what so ever it just won't work.