V8 + Win NT Beginner Questions
I am finding my way with linux, and enjoying it (apart from the occasional glitch (new user problem or stuff up). Presently I have two SuSE V8 PC's on a small Lan with a Win NT4 PC still operating as the gateway to the net, and with the printer connected on LPT1. One SuSE PC is fine, can ping the NT PC and the NT4 shows that linux PC (Loft) in network neighbourhood. The second SuSE PC (Penguin) can ping the NT4 PC, and the NT4 can ping penguin. However Windows network neighbourhood does not show penguin, and using tools to find penguin or its ip 192.168.0.5 fails. Any ideas here would be appreciated. Secondly, I have been attempting to set up the Lexmark laser on the NT4 PC as a network printer using CUPS. From Yast2 I have gone to setup the "printers in Cups" and whereas the connection lookup will find, Loft & penguin OK, there is no sign of the NT4 PC I think that this is preventing me connecting to the printer, and I have been unable to test print from penguin. Any ideas appreciated.-- John Blue, PO Box 542 Mawson ACT 2607 Australia email: jblue@bestpond.com Fax: +61 2 6291 1119 This email has been pre-scanned using the latest Anti Virus software for your peace of mind. Please remember to maintain your own anti virus up to date with the latest reference files.
John, The first step in resolving your problem is to make sure each system can ping the IP address of the others. Start by checking link lights on your hub and network cards (if present). Next, verify that each system has an IP address. Are you using static addresses or DHCP? The commands in linux are ifconfig eth0 (run as root in a terminal window) and in NT the command is ipconfig /all (run as anyuser at a command prompt). All internal network connections (both linux boxes and the internal NIC on the NT machine) should have addresses that are similar - 192.168.0.AAA with an identical subnet mask. The default gateway on both suse machines should be the internal nic on the nt box. Your settings should be something like the following: NT Box IP 192.168.0.1 Subnet Mask 255.255.255.0 Loft IP 192.168.0.2 SM 255.255.255.0 Default Gateway 192.168.0.1 Penguin IP 192.168.0.3 SM 255.255.255.0 DG 192.168.0.1 Each machine should be able to ping it's counterparts. If Loft can see the NT box and the NT box can ping Loft, but neither can see Penguin then start by checking the cabling and then the network setup on Penguin. Once Penguin can be pinged then we can look at the Samba setup to make have Penguin show up in the network neighborhood. I hope this hasn't been too basic. Let me know how else I can help. Regards, Joel Vande Berg San Diego, CA USA vanguard@phoboslabs.com Next,
I am finding my way with linux, and enjoying it (apart from the occasional glitch (new user problem or stuff up).
Presently I have two SuSE V8 PC's on a small Lan with a Win NT4 PC still operating as the gateway to the net, and with the printer connected on LPT1.
One SuSE PC is fine, can ping the NT PC and the NT4 shows that linux PC (Loft) in network neighbourhood.
The second SuSE PC (Penguin) can ping the NT4 PC, and the NT4 can ping penguin. However Windows network neighbourhood does not show penguin, and using tools to find penguin or its ip 192.168.0.5 fails.
Any ideas here would be appreciated.
Secondly, I have been attempting to set up the Lexmark laser on the NT4 PC as a network printer using CUPS. From Yast2 I have gone to setup the "printers in Cups" and whereas the connection lookup will find, Loft & penguin OK, there is no sign of the NT4 PC
I think that this is preventing me connecting to the printer, and I have been unable to test print from penguin.
Any ideas appreciated.-- John Blue, PO Box 542 Mawson ACT 2607 Australia email: jblue@bestpond.com Fax: +61 2 6291 1119
This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
Please remember to maintain your own anti virus up to date with the latest reference files.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi Joel, Thanks for the response.
John,
The first step in resolving your problem is to make sure each system can ping the IP address of the others. Start by checking link lights on your hub and network cards (if present).
Ok. Penguin is the problem, Loft is OK. A quick check of NIC lights indicates all functioning. Each PC can ping all others on the network. I can also browse the internet from each PC. Hardware wise the NT box (P111) has two NIC's one connected to the home network as 192.168.0.1 and is the gateway. The second NIC connects to the ADSL modem with a dynamic address, which only changes on a reboot (being NT this is more often than I would like :) )
Next, verify that each system has an IP address. Are you using static addresses or DHCP? The commands in linux are ifconfig eth0 (run as root in a terminal window) and in NT the command is ipconfig /all (run as anyuser at a command prompt).
Using static addresses internally, ADSL connection is DHCP.
All internal network connections (both linux boxes and the internal NIC on the NT machine) should have addresses that are similar - 192.168.0.AAA with an identical subnet mask. The default gateway on both suse machines should be the internal nic on the nt box. Your settings should be something like the following:
As above, all OK. ip's are 192.168.0.1,2 & 5 I also connect a notebook (Win2K) without problems as 192.168.0.3
NT Box
IP 192.168.0.1 Subnet Mask 255.255.255.0
Loft
IP 192.168.0.2 SM 255.255.255.0 Default Gateway 192.168.0.1
Penguin
IP 192.168.0.3 in my case x.x.x.5 SM 255.255.255.0 DG 192.168.0.1
OK as above.
Each machine should be able to ping it's counterparts. If Loft can see the NT box and the NT box can ping Loft, but neither can see Penguin then start by checking the cabling and then the network setup on Penguin.
Both P111(NT) & Penguin can ping each other OK. However I notice that the time from penguin to P111 is >=800ms and goes to 1.8. whereas normally P111 to loft or P111 to penguin is around 255ms.
Once Penguin can be pinged then we can look at the Samba setup to make have Penguin show up in the network neighborhood.
Pings OK (although slow) and from Penguin I can run Linneighborhood and mount drives from P111 on penguin. Problem remains, penguin not visible in p111 network neighbourhood.
I hope this hasn't been too basic. Thanks Joel, but before we run, we learn to walk, and before we walk we usually crawl. I appreciate you being back at basics.
Let me know how else I can help. My real aim here is to get the Lexmark laser on P111-LPT1 to be accessible via CUPS across the network.
Thanks for the help. John
Regards,
Joel Vande Berg San Diego, CA USA vanguard@phoboslabs.com
Next,
I am finding my way with linux, and enjoying it (apart from the occasional glitch (new user problem or stuff up).
Presently I have two SuSE V8 PC's on a small Lan with a Win NT4 PC still operating as the gateway to the net, and with the printer connected on LPT1.
One SuSE PC is fine, can ping the NT PC and the NT4 shows that linux PC (Loft) in network neighbourhood.
The second SuSE PC (Penguin) can ping the NT4 PC, and the NT4 can ping penguin. However Windows network neighbourhood does not show penguin, and using tools to find penguin or its ip 192.168.0.5 fails.
Any ideas here would be appreciated.
Secondly, I have been attempting to set up the Lexmark laser on the NT4 PC as a network printer using CUPS. From Yast2 I have gone to setup the "printers in Cups" and whereas the connection lookup will find, Loft & penguin OK, there is no sign of the NT4 PC
I think that this is preventing me connecting to the printer, and I have been unable to test print from penguin.
Any ideas appreciated.-- John Blue, PO Box 542 Mawson ACT 2607 Australia email: jblue@bestpond.com Fax: +61 2 6291 1119
This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
Please remember to maintain your own anti virus up to date with the latest reference files.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
This email has been pre-scanned using the latest Anti Virus software for your peace of mind. Please remember to maintain your own anti virus up to date with the latest reference files.
Joel & Jon, Thanks for the help. I have resolved one of the problems, and can now see Penguin in the NT Network neighbourhood. It appears I made a classic stuff up in the Samba config on Penguin, by entering the wrong netbios name. As soon as I corrected this penguin became visible in Network neighbourhood. Still trying to get the printing working via Cups, from Yast2 only Loft & penguin appear when using the lookup facility, P111 (NT4 PC) does not appear. So I will keep working on it. Thanks, John
I am finding my way with linux, and enjoying it (apart from the occasional glitch (new user problem or stuff up).
Presently I have two SuSE V8 PC's on a small Lan with a Win NT4 PC still operating as the gateway to the net, and with the printer connected on LPT1.
One SuSE PC is fine, can ping the NT PC and the NT4 shows that linux PC (Loft) in network neighbourhood.
The second SuSE PC (Penguin) can ping the NT4 PC, and the NT4 can ping penguin. However Windows network neighbourhood does not show penguin, and using tools to find penguin or its ip 192.168.0.5 fails.
Any ideas here would be appreciated.
Secondly, I have been attempting to set up the Lexmark laser on the NT4 PC as a network printer using CUPS. From Yast2 I have gone to setup the "printers in Cups" and whereas the connection lookup will find, Loft & penguin OK, there is no sign of the NT4 PC
I think that this is preventing me connecting to the printer, and I have been unable to test print from penguin.
Any ideas appreciated.-- John Blue, PO Box 542 Mawson ACT 2607 Australia email: jblue@bestpond.com Fax: +61 2 6291 1119
This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
Please remember to maintain your own anti virus up to date with the latest reference files.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
This email has been pre-scanned using the latest Anti Virus software for your peace of mind. Please remember to maintain your own anti virus up to date with the latest reference files.
John, At this point your past what I've normally done. Since your sharing the printer from the windows machine I think I would start there. Is P111 a domain controller or a member server? And if it's a domain controller, did you run add computer accounts for Penguin and Loft, and then run smbpassword on each client to add them to the domain. This is required before the clients can access the domain. If this is successful you should be able to see both loft and penguin in server manager on P111. Server manager is Start > Programs > Administrative Tools > Server Manager. Let us know if it works. HTH. Joel
Joel & Jon,
Thanks for the help.
I have resolved one of the problems, and can now see Penguin in the NT Network neighbourhood.
It appears I made a classic stuff up in the Samba config on Penguin, by entering the wrong netbios name. As soon as I corrected this penguin became visible in Network neighbourhood.
Still trying to get the printing working via Cups, from Yast2 only Loft & penguin appear when using the lookup facility, P111 (NT4 PC) does not appear.
So I will keep working on it.
Thanks, John
I am finding my way with linux, and enjoying it (apart from the occasional glitch (new user problem or stuff up).
Presently I have two SuSE V8 PC's on a small Lan with a Win NT4 PC still operating as the gateway to the net, and with the printer connected on LPT1.
One SuSE PC is fine, can ping the NT PC and the NT4 shows that linux PC (Loft) in network neighbourhood.
The second SuSE PC (Penguin) can ping the NT4 PC, and the NT4 can ping penguin. However Windows network neighbourhood does not show penguin, and using tools to find penguin or its ip 192.168.0.5 fails.
Any ideas here would be appreciated.
Secondly, I have been attempting to set up the Lexmark laser on the NT4 PC as a network printer using CUPS. From Yast2 I have gone to setup the "printers in Cups" and whereas the connection lookup will find, Loft & penguin OK, there is no sign of the NT4 PC
I think that this is preventing me connecting to the printer, and I have been unable to test print from penguin.
Any ideas appreciated.-- John Blue, PO Box 542 Mawson ACT 2607 Australia email: jblue@bestpond.com Fax: +61 2 6291 1119
This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
Please remember to maintain your own anti virus up to date with the latest reference files.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
Please remember to maintain your own anti virus up to date with the latest reference files.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi Joel, Thanks for the advice.
John,
At this point your past what I've normally done. Since your sharing the printer from the windows machine I think I would start there. Is P111 a domain controller or a member server?
P111 is simply running NT4 (sp6a) Workstation (not server). I haven't setup a specific domain controller as such (unless I have misunderstood some aspects of the installation)
And if it's a domain controller, did you run add computer accounts for Penguin and Loft, and then run smbpassword on each client to add them to the domain. This is required before the clients can access the domain. If this is successful you should be able to see both loft and penguin in server manager on P111.
I can now see all computers in the P111 network neighbourhood! Although I don't yet have access to penguin. I gather this is probably a samba configuration issue on penguin, so I will review the samba troubleshooting guide. Thanks for the guidance, I will come back to the list if I need more advice, but in the meantime I think I'd better check through the online materials again. Best wishes, John
Server manager is Start > Programs > Administrative Tools > Server Manager.
Let us know if it works.
HTH.
Joel
Joel & Jon,
Thanks for the help.
I have resolved one of the problems, and can now see Penguin in the NT Network neighbourhood.
It appears I made a classic stuff up in the Samba config on Penguin, by entering the wrong netbios name. As soon as I corrected this penguin became visible in Network neighbourhood.
Still trying to get the printing working via Cups, from Yast2 only Loft & penguin appear when using the lookup facility, P111 (NT4 PC) does not appear.
So I will keep working on it.
Thanks, John
I am finding my way with linux, and enjoying it (apart from the occasional glitch (new user problem or stuff up).
Presently I have two SuSE V8 PC's on a small Lan with a Win NT4 PC still operating as the gateway to the net, and with the printer connected on LPT1.
One SuSE PC is fine, can ping the NT PC and the NT4 shows that linux PC (Loft) in network neighbourhood.
The second SuSE PC (Penguin) can ping the NT4 PC, and the NT4 can ping penguin. However Windows network neighbourhood does not show penguin, and using tools to find penguin or its ip 192.168.0.5 fails.
Any ideas here would be appreciated.
Secondly, I have been attempting to set up the Lexmark laser on the NT4 PC as a network printer using CUPS. From Yast2 I have gone to setup the "printers in Cups" and whereas the connection lookup will find, Loft & penguin OK, there is no sign of the NT4 PC
I think that this is preventing me connecting to the printer, and I have been unable to test print from penguin.
Any ideas appreciated.-- John Blue, PO Box 542 Mawson ACT 2607 Australia email: jblue@bestpond.com Fax: +61 2 6291 1119
This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
Please remember to maintain your own anti virus up to date with the latest reference files.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
This email has been pre-scanned using the latest Anti Virus software for your peace of mind.
Please remember to maintain your own anti virus up to date with the latest reference files.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
This email has been pre-scanned using the latest Anti Virus software for your peace of mind. Please remember to maintain your own anti virus up to date with the latest reference files.
participants (2)
-
Joel Vande Berg -
John Blue