I am trying to set up a redhat 6.0 server at home so i can program at home and test. I have two other win98 based systems and wish to be able to connect to the server via ftp/telnet if possible or just via network neighborhood. I have set up the server with 200.200.200.100 static IP address and have tested the eht0 card via telnet on the server and had no problem. I cannot get the win98 systems to do anything with the server at all. I have tried to install Microsoft Client and input address of 200.200.200.101 for the other system and netmask of 255.255.255.0. NOTHING Anyone that can tell me how to do this?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Home Server with Redhat as host and connect with win98 system 1
- Thread starter pltdaddy
- Start date
-
1
- #2
Sounds like you've started off OK, but I need a bit more info.<br>
<br>
Can you ping the Linux server from the Win98 boxes? Can each Win98 box ping the other? How are the boxes linked into your home network? What's the netmask on the Linux server? Which Microsoft Client have you tried installing? Can the Win98 machines see each other in Network Neighbourhood?
<br>
Can you ping the Linux server from the Win98 boxes? Can each Win98 box ping the other? How are the boxes linked into your home network? What's the netmask on the Linux server? Which Microsoft Client have you tried installing? Can the Win98 machines see each other in Network Neighbourhood?
- Thread starter
- #3
How do you ping the server? Each Win 98 can network. I had them configured in WIN LOGIN and no problems. I have not tried to get them to link under my current attempt as microsoft client. I have now set up network on my win 98 box as Microsoft Client. All boxes are connected via MiniMMAC Cabletron 12 port hub. All boxes were connected as WIN 98 boxes via same cabling etc. I just killed the WIN on one box and am converting to Linux. The Server is not online, just to be sure you know that. The server setup is :<br>
<br>
HOST: 200.200.200.100<br>
Netmask : 255.255.255.0<br>
broadcast : 200.200.200.255<br>
gateway: 200.200.200.254<br>
<br>
I have the other boxes configured as<br>
<br>
comp1: 200.200.200.101<br>
comp2: 200.200.200.102<br>
<br>
I have configured the network in the linux box for<br>
<br>
names <br>
hostname: .plt.com<br>
domain : plt.com<br>
nameserver: 200.200.200.1<br>
<br>
hosts<br>
127.0.0.1 localhost<br>
200.200.200.100 .plt.com<br>
200.200.200.101 comp1<br>
200.200.200.102 comp2<br>
<br>
<br>
HOST: 200.200.200.100<br>
Netmask : 255.255.255.0<br>
broadcast : 200.200.200.255<br>
gateway: 200.200.200.254<br>
<br>
I have the other boxes configured as<br>
<br>
comp1: 200.200.200.101<br>
comp2: 200.200.200.102<br>
<br>
I have configured the network in the linux box for<br>
<br>
names <br>
hostname: .plt.com<br>
domain : plt.com<br>
nameserver: 200.200.200.1<br>
<br>
hosts<br>
127.0.0.1 localhost<br>
200.200.200.100 .plt.com<br>
200.200.200.101 comp1<br>
200.200.200.102 comp2<br>
<br>
I've not got Win98, but I'm assuming that it's just Win95 plus IE4/IE5, Active Desktop, and some new drivers ;^). So, all the Windows stuff below is based on Win95.<br>
<br>
OK, the Win Login was probably using NetBEUI (Microsoft Networking) as it's protocol. This is the default for Microsoft Networking. (Or, it used to be.) The Win98 boxes will also be using this to see each other's shared drives and printers. To connect to the server you need TCP/IP.<br>
<br>
Because you've set up IP addresses on the Win98 boxes, this must mean TCP/IP is installed. (I also recall something about TCP/IP being available by default in Win98.)<br>
<br>
The set up you've detailed should work OK, although you should consider changing your network address to be in the 192.168 "public use" range. Then, if you do hook up your network to the Net, there shouldn't be any problems with clashing IP numbers.<br>
<br>
When you say the the "... server is not online...", I'm assuming you mean that it's not got an Internet connection, and not that it's powered off. ;^D<br>
<br>
OK, to ping the server from the Win boxes, start up a DOS box/command prompt/whatever it's called these days. In the DOS box, type:<br>
<br>
ping 200.200.200.100<br>
<br>
You should see something like:<br>
<br>
C:\WINDOWS>ping 200.200.200.100<br>
<br>
Pinging 200.200.200.100 with 32 bytes of data:<br>
<br>
Reply from 200.200.200.100: bytes=32 time=1ms TTL=63<br>
Reply from 200.200.200.100: bytes=32 time<10ms TTL=63<br>
Reply from 200.200.200.100: bytes=32 time=1ms TTL=63<br>
Reply from 200.200.200.100: bytes=32 time<10ms TTL=63<br>
<br>
<br>
If this works, then TCP/IP is configured and working at both ends. If you see "Request timed out" instead of the "Reply from..." messages above, then TCP/IP is failing on either the Win98 box or the Linux server.<br>
<br>
If TCP/IP ping failed:<br>
======================<br>
Login to the Linux box as root.<br>
<br>
Type "netstat -i".<br>
<br>
You'll see some output about the network interfaces that are currently recognised by Linux. You'll always have at least one interface for the loopback device called "lo" or "lo0". You should see another. It's name will vary depending on the network card in the Linux box, but could be something like "eE0", "eth0", or something.<br>
<br>
If you don't see this second device, then Linux is not recognising your network card, and that's your problem.<br>
<br>
<br>
If TCP/IP ping worked OK:<br>
=========================<br>
Then TCP/IP is up and running. The next thing to try is to telnet from a Win98 box to the server. From a DOS box again, type:<br>
<br>
telnet 200.200.200.100<br>
<br>
A Windows telnet window should appear, and you should see the login prompt from the Linux box.<br>
<br>
A quick word on telnet. You said that you'd telnetted on the server. I'm assuming that you were logged in to the Linux server, and did something like "telnet 200.200.200.100" to telnet back in to yourself. IF this was the case, you didn't touch the ethernet card at all.<br>
<br>
Linux, and Unix in general, doesn't use the ethernet card for local networking operations. It uses the loopback device mentioned earlier. On my standalone Linux box at home, I can telnet and rlogin back in to the box without having a network card. X does all it's work via networking, and this also uses the loopback device if running locally.<br>
<br>
Don't worry about this too much, I just thought I'd mention it cos it's a common mistake to assume that because you can network from the current host to the current host, networking is up and running.<br>
<br>
A point on the name of the Linux server, also. The hostname looks a bit bogus, and might cause problems. You should change ".plt.com" to be something like "myserver.plt.com".<br>
<br>
Finally, and you probably know this already, the Microsoft equiv of /etc/hosts is c:\windows\lmhosts. It's the same format, so just set it up as you would the Linux /etc/hosts.<br>
<br>
OK, I've rambled on enough for now. Sorry if it's made no sense, but I'm getting over major jet lag at the mo.
<br>
<br>
Let me know how you get on.
<br>
OK, the Win Login was probably using NetBEUI (Microsoft Networking) as it's protocol. This is the default for Microsoft Networking. (Or, it used to be.) The Win98 boxes will also be using this to see each other's shared drives and printers. To connect to the server you need TCP/IP.<br>
<br>
Because you've set up IP addresses on the Win98 boxes, this must mean TCP/IP is installed. (I also recall something about TCP/IP being available by default in Win98.)<br>
<br>
The set up you've detailed should work OK, although you should consider changing your network address to be in the 192.168 "public use" range. Then, if you do hook up your network to the Net, there shouldn't be any problems with clashing IP numbers.<br>
<br>
When you say the the "... server is not online...", I'm assuming you mean that it's not got an Internet connection, and not that it's powered off. ;^D<br>
<br>
OK, to ping the server from the Win boxes, start up a DOS box/command prompt/whatever it's called these days. In the DOS box, type:<br>
<br>
ping 200.200.200.100<br>
<br>
You should see something like:<br>
<br>
C:\WINDOWS>ping 200.200.200.100<br>
<br>
Pinging 200.200.200.100 with 32 bytes of data:<br>
<br>
Reply from 200.200.200.100: bytes=32 time=1ms TTL=63<br>
Reply from 200.200.200.100: bytes=32 time<10ms TTL=63<br>
Reply from 200.200.200.100: bytes=32 time=1ms TTL=63<br>
Reply from 200.200.200.100: bytes=32 time<10ms TTL=63<br>
<br>
<br>
If this works, then TCP/IP is configured and working at both ends. If you see "Request timed out" instead of the "Reply from..." messages above, then TCP/IP is failing on either the Win98 box or the Linux server.<br>
<br>
If TCP/IP ping failed:<br>
======================<br>
Login to the Linux box as root.<br>
<br>
Type "netstat -i".<br>
<br>
You'll see some output about the network interfaces that are currently recognised by Linux. You'll always have at least one interface for the loopback device called "lo" or "lo0". You should see another. It's name will vary depending on the network card in the Linux box, but could be something like "eE0", "eth0", or something.<br>
<br>
If you don't see this second device, then Linux is not recognising your network card, and that's your problem.<br>
<br>
<br>
If TCP/IP ping worked OK:<br>
=========================<br>
Then TCP/IP is up and running. The next thing to try is to telnet from a Win98 box to the server. From a DOS box again, type:<br>
<br>
telnet 200.200.200.100<br>
<br>
A Windows telnet window should appear, and you should see the login prompt from the Linux box.<br>
<br>
A quick word on telnet. You said that you'd telnetted on the server. I'm assuming that you were logged in to the Linux server, and did something like "telnet 200.200.200.100" to telnet back in to yourself. IF this was the case, you didn't touch the ethernet card at all.<br>
<br>
Linux, and Unix in general, doesn't use the ethernet card for local networking operations. It uses the loopback device mentioned earlier. On my standalone Linux box at home, I can telnet and rlogin back in to the box without having a network card. X does all it's work via networking, and this also uses the loopback device if running locally.<br>
<br>
Don't worry about this too much, I just thought I'd mention it cos it's a common mistake to assume that because you can network from the current host to the current host, networking is up and running.<br>
<br>
A point on the name of the Linux server, also. The hostname looks a bit bogus, and might cause problems. You should change ".plt.com" to be something like "myserver.plt.com".<br>
<br>
Finally, and you probably know this already, the Microsoft equiv of /etc/hosts is c:\windows\lmhosts. It's the same format, so just set it up as you would the Linux /etc/hosts.<br>
<br>
OK, I've rambled on enough for now. Sorry if it's made no sense, but I'm getting over major jet lag at the mo.
<br><br>
Let me know how you get on.
- Thread starter
- #5
The ethernet card;while detected, was not functioning(Time out error). I replaced the card and am now running the server. I cannot locate any boxes in the Network neighborhood, but I did FTP into the server and linked via web to my new OFFline homepage. SO COOL. Thank you for your help.
To access filesystems and printers on the linux box from windows, you need to be running samba. Make sure you have it<br>
installed and running (try "netstat -a ¦ grep -i netbios" on Linux, it should show 3 open ports).<br>
<br>
You may also have to edit your setup (in /etc/smb.conf, but read the documentation under /usr/doc/samba-* first!), especially the workgroup should be the same as on the windows boxes).<br>
<br>
Finally, samba and Win98 (and WinNT SP4) use different password schemes by default, so you cannot access any shares, before you have changed either the samba or the win98 setup - I suggest you copy Win98_PlainPassword.reg to the win98 boxes and double-click on it, its simpler than changing the server to accept NT-style password hashes.<br>
installed and running (try "netstat -a ¦ grep -i netbios" on Linux, it should show 3 open ports).<br>
<br>
You may also have to edit your setup (in /etc/smb.conf, but read the documentation under /usr/doc/samba-* first!), especially the workgroup should be the same as on the windows boxes).<br>
<br>
Finally, samba and Win98 (and WinNT SP4) use different password schemes by default, so you cannot access any shares, before you have changed either the samba or the win98 setup - I suggest you copy Win98_PlainPassword.reg to the win98 boxes and double-click on it, its simpler than changing the server to accept NT-style password hashes.<br>
- Status
Similar threads
