computer server question
07-20-2002, 07:41 PM
#1
Senior Member
Thread Starter
Join Date: Nov 2001
Location: MIA
Posts: 989
Well anyways, I had it for a while now and trying to set-up a network at home. I'm running Windows NT 4.1 on the server, Windows XP in the PC in my room, and Windows 98 (HP Pavilion) in the family room.
So far I got my computer into the network neighborhood and it shows the server and vice versa. I can't get the Win 98 computer to show though or get the printer to work via the network.
Is there a conflict with Windows 98 or something ? it's really pissing me off
I read through the MS Windows NT Server book and bought a Windows NT book by Sams, but I'm still clueless on why it's not connecting...
Any ideas ?
So far I got my computer into the network neighborhood and it shows the server and vice versa. I can't get the Win 98 computer to show though or get the printer to work via the network.
Is there a conflict with Windows 98 or something ? it's really pissing me off
I read through the MS Windows NT Server book and bought a Windows NT book by Sams, but I'm still clueless on why it's not connecting...
Any ideas ?
07-21-2002, 09:32 AM
#4
Senior Member
Join Date: Feb 2002
Location: Close enough to annoy you.
Posts: 1,381
You got NT 3.1 running? Wow. Talk about a heap o junk!
Rule 1: Never trust the network browser it's NOT reliable.
2nd Question: Are you running TCP/IP as your protocol? If so the only way the 98 box is going to see the NT server is if you're run WINS or an LMHOSTS file.
I'll explain how it's done if ya need it.
Horn you're correct that 98 cannot see the NTFS file system, but that only applies if you're dual booting.
Rule 1: Never trust the network browser it's NOT reliable.
2nd Question: Are you running TCP/IP as your protocol? If so the only way the 98 box is going to see the NT server is if you're run WINS or an LMHOSTS file.
I'll explain how it's done if ya need it.
Horn you're correct that 98 cannot see the NTFS file system, but that only applies if you're dual booting.
07-21-2002, 10:40 AM
#5
Senior Member
Thread Starter
Join Date: Nov 2001
Location: MIA
Posts: 989
Originally Posted by Rotarydragon' date='Jul 21 2002, 10:32 AM
2nd Question: Are you running TCP/IP as your protocol? If so the only way the 98 box is going to see the NT server is if you're run WINS or an LMHOSTS file.
yes I do have the TCP/IP protocol.
what do you recommend I do?
07-21-2002, 11:00 AM
#6
Senior Member
Join Date: Feb 2002
Location: Close enough to annoy you.
Posts: 1,381
Go into the winnt/system32/drivers/etc directory find a file called lmhosts.sam
Edit the file it should look something like:
192.168.1.1 name of the computer
Just change the IP address and the name to match
You'll have to do that on each and every system. I don't remember where the lmhosts file is on Win98.
The other option is to add the WINS service to the NT box, but I honestly don't remember if NT 3.1 had WINS.
Get NT 4 or better
Edit the file it should look something like:
192.168.1.1 name of the computer
Just change the IP address and the name to match
You'll have to do that on each and every system. I don't remember where the lmhosts file is on Win98.
The other option is to add the WINS service to the NT box, but I honestly don't remember if NT 3.1 had WINS.
Get NT 4 or better
07-21-2002, 01:06 PM
#7
Senior Member
Thread Starter
Join Date: Nov 2001
Location: MIA
Posts: 989
Originally Posted by Rotarydragon' date='Jul 21 2002, 12:00 PM
Go into the winnt/system32/drivers/etc directory find a file called lmhosts.sam
Edit the file it should look something like:
192.168.1.1 name of the computer
Just change the IP address and the name to match
You'll have to do that on each and every system. I don't remember where the lmhosts file is on Win98.
The other option is to add the WINS service to the NT box, but I honestly don't remember if NT 3.1 had WINS.
Get NT 4 or better
Edit the file it should look something like:
192.168.1.1 name of the computer
Just change the IP address and the name to match
You'll have to do that on each and every system. I don't remember where the lmhosts file is on Win98.
The other option is to add the WINS service to the NT box, but I honestly don't remember if NT 3.1 had WINS.
Get NT 4 or better
Where can I find NT 4 cheap :unsure:
07-21-2002, 07:48 PM
#9
Senior Member
Join Date: Oct 2001
Location: Portland, OR
Posts: 790
1. Make sure the workgroup names are all the same.
2. Are you logging into a Domain? Is the NT 3.51 your PDC?
You don't need Wins or LMhosts to see machines in the network neighborhood. But Wins wouldn't be a bad idea.
There are tools you can get from the NT Resource kit that will help here. DOMON and BROWSEMON (<- I think those are the names) will show you which machine is the master browser. It could be that XP is fighting your Server for control. You'll see this in the event viewer on the server side.
Also you might try adding NETBEUI to all your machines to make sure it's not a TCP problem.
Good Luck
2. Are you logging into a Domain? Is the NT 3.51 your PDC?
You don't need Wins or LMhosts to see machines in the network neighborhood. But Wins wouldn't be a bad idea.
There are tools you can get from the NT Resource kit that will help here. DOMON and BROWSEMON (<- I think those are the names) will show you which machine is the master browser. It could be that XP is fighting your Server for control. You'll see this in the event viewer on the server side.
Also you might try adding NETBEUI to all your machines to make sure it's not a TCP problem.
Good Luck
07-21-2002, 08:48 PM
#10
Senior Member
Join Date: Feb 2002
Location: Close enough to annoy you.
Posts: 1,381
Originally Posted by dac' date='Jul 22 2002, 03:48 AM
1. Make sure the workgroup names are all the same.
2. Are you logging into a Domain? Is the NT 3.51 your PDC?
You don't need Wins or LMhosts to see machines in the network neighborhood. But Wins wouldn't be a bad idea.
There are tools you can get from the NT Resource kit that will help here. DOMON and BROWSEMON (<- I think those are the names) will show you which machine is the master browser. It could be that XP is fighting your Server for control. You'll see this in the event viewer on the server side.
Also you might try adding NETBEUI to all your machines to make sure it's not a TCP problem.
Good Luck
2. Are you logging into a Domain? Is the NT 3.51 your PDC?
You don't need Wins or LMhosts to see machines in the network neighborhood. But Wins wouldn't be a bad idea.
There are tools you can get from the NT Resource kit that will help here. DOMON and BROWSEMON (<- I think those are the names) will show you which machine is the master browser. It could be that XP is fighting your Server for control. You'll see this in the event viewer on the server side.
Also you might try adding NETBEUI to all your machines to make sure it's not a TCP problem.
Good Luck
You need LMHosts or WINS to see anything in network neighbohood if you're running TCP/IP, that's where it generates it's lists.
Further NT uses LMAUTH 2 package to authenticate, it won't find anything on IP without them from a 98 box, it pretty much ignores the broadcasts.
Workgroup names won't stop you from connecting, it will stop you from seeing things. Never ever trust the browser, it can be up to 15 min to a hour out of date at any given time. It's cranky otherwise.
As far as master browser goes, this is again why you need the lmhosts or WINS files/services running. As I recal XP Pro will not declare itself master in the presence of an NT 4 box but that may well not apply to NT 3.1 which is not the same ball of wax.
NetBEUI would work as it's bulletproof in all cases.