Let me explain what I have and what I want to accomplish. I have an AT&T wireless router. My main computer is a Linux 12.2 64 bit machine which is hard wired to the wireless router, at the point of DSL entry. Also hard wired to the router is another older Linux machine which I have not yet upgraded. It is running OpenSuse 11.3. I have two Windows XP machines which have wireless modems. I want to share the same printer and files on all four machines. The printer is attached to one of the wireless Windows XP machines.
I have no idea where to start. Should I set up a wireless network with the 2 XP machines and then use Samba to tie in the Linux machines? Would that work?
Thanks for any help that anyone can give. . .much appreciated.
On 09/14/2012 10:46 PM, jdcart15 wrote:
> nt to
By xp machines with “modems”, I assume that they connect to the internet
via the router – and I assume the hard wired machines (I assume that
means ethernet cabling) connect to the internet that way too, is that right?
So yes, implement a Samba network. “samba” is the Linux expression for
“windows networking and sharing”. Here’s a burst on setting up a
workstation to connect to a “windows networking and sharing” LAN: http://www.swerdna.net.au/suselanprimer.html
On 09/14/2012 10:56 PM, swerdna wrote:
> On 09/14/2012 10:46 PM, jdcart15 wrote:
>> nt to
> By xp machines with “modems”, I assume that they connect to the internet
> via the router – and I assume the hard wired machines (I assume that
> means ethernet cabling) connect to the internet that way too, is that
> right?
>
> So yes, implement a Samba network. “samba” is the Linux expression for
> “windows networking and sharing”. Here’s a burst on setting up a
> workstation to connect to a “windows networking and sharing” LAN:
> http://www.swerdna.net.au/suselanprimer.html
>
>
>
The article badly needs updating – but the method is right.
Thank you swerdna. Yes, your assumptions are correct. Tell me if my strategy is on track. I would like to share files and printer via the two wireless xp machines before I proceed the two Ethernet Linux machines. Right now the At&t firewall is configured such that I am having a hard time getting the two wireless xp machines to see each other. Until I accomplish this I am not going further. AT&T wants me to pay to get help, and I would like to figure it out myself. AT&T, in my opinion is a lousy provider, but it is the only real choice that I have. Any help from anybody here would be much appreciated. jdcart
On 09/15/2012 11:06 AM, jdcart15 wrote:
>
> Thank you swerdna. Yes, your assumptions are correct. Tell me if my
> strategy is on track. I would like to share files and printer via the
> two wireless xp machines before I proceed the two Ethernet Linux
> machines. Right now the At&t firewall is configured such that I am
> having a hard time getting the two wireless xp machines to see each
> other. Until I accomplish this I am not going further. AT&T wants me
> to pay to get help, and I would like to figure it out myself. AT&T, in
> my opinion is a lousy provider, but it is the only real choice that I
> have. Any help from anybody here would be much appreciated. jdcart
>
>
What’s the model of the at&t router and perhaps a link to the exact
device on line?
My idea was to set up a Microsoft network on the two xp wireless machines and then use Samba to tie into that. But it being a wireless Microsoft network can Samba connect with that? Is this a good strategy?
My router is a 2WIRE. Do you want the ip address of my AT&T system page?
If the wirelss (xp) and the wired (Linux) computers are getting their IP addresses from the router (the default) they should be on the same network (aka LAN, aka windows network, aka Samba network, all the same thing).
Maybe they are networking properly, let’s see:
Power them all on.
In windows open a command prompt (start –> run –> cmd) and enter ipconfig. Report back here the “IP address” and the “Default gateway” for each of the two xp machines.
In Liunx open a console window and enter /sbin/ifconfig. Get the interface IP address from line 2 of the first paragraph. Report it here for each Linux machine.
In Linux open a console window and enter /sbin/route. Get the gateway IP address from the entry before the asterisk in the last line. Report it here for each Linux machine.
I guess the network is in place, all I need to do is learn how to configure the firewall to let me see all of these machines, on each computer? Maybe I pay for AT&T help? That is certainly what they want. They want to keep you in the dark so you will pay them to set it up for you, I think. Thanks for your help. . .much appreciated.
I would set the IPs of the Linux boxes in yast to be fixed IP addresses with gateways at 192.168.1.254 and Name Servers (DNS servers) at 8.8.8.8 and 8.8.4.4. The fixed IPs would be 192.168.1.40 and 192.168.1.41
The only firewall you need to consider (I think, not certain) is the internal openSUSE firewall, but at this stage ignore that and just get the IPs set right, and check you can browse the internet from them.
On 09/16/2012 09:56 PM, swerdna wrote:
>
> jdcart15;2487565 Wrote:
>> I guess the network is in place, all I need to do is learn how to
>> configure the firewall to let me see all of these machines, on each
>> computer? Maybe I pay for AT&T help? That is certainly what they want.
>> They want to keep you in the dark so you will pay them to set it up
>> for you, I think. Thanks for your help. . .much appreciated.
>
> I would set the IPs of the Linux boxes in yast to be fixed IP addresses
> with gateways at 192.168.1.254 and Name Servers (DNS servers) at 8.8.8.8
> and 8.8.4.4. The fixed IPs would be 192.168.1.40 and 192.168.1.41
> The only firewall you need to consider (I think, not certain) is the
> internal openSUSE firewall, but at this stage ignore that and just get
> the IPs set right, and check you can browse the internet from them.
>
>
I forgot: first I would ping the addresses 192.168.1.40 and 41 before
using them, to make sure they are unused.
On 2012-09-16 00:16, jdcart15 wrote:
>
> cont. from previous accidental post
> Linux 32 bit ethernet
> gateway IP 192.168.1.0
>
> XP-Laptop
> IP 192.168.164
> DG 192.168.1.254
>
> XP Desktop
> IP 192.168.1.65
> DG 192.168.1.254
Make sure that all machines have the same gateway defined. The only number that can be, and has
to be, different, is the IP, but in the same range.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
thank you. If I am not mistaking, the gateway address is the one ending in 254, and this would be for all four machines? The ip address varies by the last number via the DCHP function. I am traveling at the moment but will pick up on this when I return home.
On 09/21/2012 12:16 AM, jdcart15 wrote:
>
> I forgot: first I would ping the addresses 192.168.1.40 and 41 before
> using them, to make sure they are unused.
>
>
> When I ping these addresses: I get a reply from 192.168.1.71 that
> “Destination Host Unreachable”
>
>
That’s good. It means the addresses are not being used, so you can go
ahead and use them.
On 2012-09-17 20:56, jdcart15 wrote:
>
> thank you. If I am not mistaking, the gateway address is the one ending
> in 254, and this would be for all four machines? The ip address varies
> by the last number via the DCHP function. I am traveling at the moment
> but will pick up on this when I return home.
No.
You previously wrote:
> cont. from previous accidental post
> Linux 32 bit ethernet
> gateway IP 192.168.1.0
so the gateway would be “192.168.1.0” - but it happens, and I did not notice before, that an address
ending in zero is not valid (it is the address of the network). That setting can not work.
Typically the gateway is the address of your router to internet, and it would probably be “192.168.1.1”.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))