Because SMB servers can't push/pull files to and from a client. And it removes the need for any special configuration on the client beyond sharing a directory.
But clients can push to the server surely? It just seems like an awful lot of work that could be avoided.
quality thanks man iwill try this on the weekend or when my server decided to show itself to the world again as at the moment cant access it remotely. seems like my router dynamicaly changed its local IP again even though i got it setup using a static ip for that ubuntu pc.
anyways i will try this later and if i have any issues i will let you guys know.
You mean you have a static DHCP reservation? It would probably be more reliable to set a static IP on the server itself.
Yea i have a static DHCP reservation. Its on a netgear DG834GT. i setup a ip reserved on my ubuntu. if there is a better way to do it. how?
Edit /etc/network/interfaces and replace:
With:allow-hotplug eth0 inet dhcp
Changing any addresses as appropriate, and replace eth0 with your adapter (likely eth0 if you only have 1 adapter).auto eth0
iface eth0 inet static
address 192.168.0.50
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
Then type
to apply the settings without needing to reboot (note this will terminate any active connections)./etc/init.d/networking restart
Last edited by watercooled; 09-04-2011 at 12:01 AM. Reason: Correction
cheers. where can i get the netmask, network, broadcast and gateway settings?
The netmask is whatever is set for your local sub-network, probably 255.255.255.0, most consumer routers use it, network address is the first address of your network, probably 192.168.0.0 with netgear defaults, broadcast is the last address of your network, probably 192.168.0.255 for netgear routers, and the gateway is just the IP address of the router, probably 192.168.0.1.
So which one do i change to setup the local static ip address of say 192.168.5 ?
Yeah, what I provided should be correct for the majority of home networks but some routers will use 192.168.1.0 or something, i.e a different third octet but I've not seen a home router that doesn't use a /24 (255.255.255.0) subnet mask, so it's safe to assume that's correct.
For example, if your router hands out 192.168.1.x addresses, then you would use:
network 192.168.1.0
broadcast 192.168.1.255
gateway - this is your router's IP address which would be 192.168.1.x (likely 192.168.1.1) in this case.
Basically, you can usually take an educated guess of all of the above knowing just the router's login IP on a home router.
Also, you should ideally pick a static IP outside of the DHCP pool to avoid IP collisions on the network, or modify the DHCP pool on the router if you want to keep the same IP for the server.
IMO setting static IPs for any permanent stuff makes things a lot easier, but leave DHCP enabled with a small pool of addresses for anything else.
ahh ok so dhcp should be from say 192.168.0.5 and any static devices i want i will add it manually from 192.168.0.2 > 192.168.0.4
There are currently 1 users browsing this thread. (0 members and 1 guests)