- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI have a PC that is connected to another subnet throught a couple of routers.
this pc is in a workgroup, with OS w98, we can call that REMOTE_PC.
on the other side, there is a NT domain: from every machine joined to this domain, I can see the directories of REMOTE_PC through normal browsing:
\\REMOTE_PC\mydir
I cannot make the same on the inverse way: I can ping other machines, I obtain the name resolution of other machines (the DNS server is in the NT domain), but I can't make the directory browsing in the same way form REMOTE_PC:
\\NT_DOMAIN_MACHINE\dir
the answer I obtain is that REMOTE_PC doesn't find NT_DOMAIN_MACHINE (but, if REMOTE_PC pings NT_DOMAIN_MACHINE, it obtains reply!)
I tried to join this REMOTE_PC to my domain, but it doesn't work (no server available...)
Another interesting thing: if I set an ODBC driver for a SQL server in the NT domain, I have connection with TCP/IP but not with named_pipe (with other PCs joining in the domain, named_pipe works with the same SQL server).
I am sure it is not a routing problem, otherwise it wouldn't work in the inverse way. I'm sure it is a problem of rights to set somewhere.
Is there anywhere something like host.allow in UNIX, i.e. a way to set other subnets to allow directory browsing to the machines of my NT domain?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: ocon827679Posted on 2003-06-13 at 07:55:31ID: 8718093
You say that the REMOTE_PC is running Win98. If this is true it will not be able to join the NT domain. Only NT, W2K, XP machines may "join" a domain. The PC should be able to participate in the domain, if the user on the PC has a domain user account. Your problem sounds like a name resolution problem. Win98, like all NT and previous MS networking operating systems don't talk DNS by default. They are NetBIOS machines and you need to be using some sort of NetBIOS name resolution. If your domain is using WINS, check the TCP/IP properties of the Win98 machine and ensure that the IP address of the WINS server is listed. If you are not using WINS, then you need to use the lmhosts file. In Win98 this is located in the Windows directory. There should be an LMHOSTS.SAM file there already. This is a sample file on how to construct the records. Check it out. If it is not there, then create a file with a text editor and call the file LMHOSTS (no extension). You need 2 records at a minimum, one for the domain and one for the domain controller.
The record format is: ip addr "domainname /0xb" for the domain. Note the domain name is 15 characters max. You must pad the domain name out 15 characters then add the /0xb at the 16th character. (It's a NetBIOS thing!) The IP address is the address of the Primary Domain Controller. the record for the domain controller is much the same: ip addr servername #PRE #DOM:domainname. Note the PRE and DOM are upper case. You should also consider placing entries for other resource servers, workstations in this file also. But that's up to you. Same format as the domain controller.
Once you have this file created, try again. You may need to reboot before it works. I don't remember what the Win98 command is to reload the NetBIOS cache, in NT it is "nbtstat -R" from the command line. It might be the same in 98. If not a reboot will reload the cache.