Having it connected to the network but not internet

Barman58 said:

Not sure if this would work on win7 - but one thing to try is to set the default gateway on the server to itself, (127.0.0.1), this should prevent the system from accessing the internet, whilst retaining access within the local subnet.

Doesn't work - it says that that address is reserved.

aem said:

Cohen said:

How do i go about IPX / SPX??

The server is on the wired network, and we have wireless which my dad & I use, as well as 2 iPod touches within the house. So i want each device / computer to be able to access the "server" via the network but not have the server connected to the internet.

Just curious how do u intend the devices to connect to the server via the network as you have stated? In all instances you will need an IP address for the server, as already mentioned you could give it a static IP, subnet and default gateway. However if you wish to connect to this server over the network and wirelessly via your router (i would assume), this could be a problem, as the router does would not have broadcasted the network that the server is configured with. Most likely you might need to configure your router to broadcast this address.

It looks for the iTunes library.... regards what the IP etc is...

And the other computers just look for the server name - Server-PC there for the address being \\Server-PC\Sharing Folder\Music

Cohen

You can only mapp drives/connect to shares if your machines are on the same vlan. If your server is wiredly connected to your modem/router, and your other devices are to wirelessly connected to your server, then 1) the server must have a wireless network card in it, correct? If so, you will need an access point (a.k.a, a router to broadcast the server's network) otherwise, i'm not sure how one wireless card can simply connected to another. Or 2) you must setup your router (which the server s connect to) to broadcast the network which the server is configured on inorder for your other devices to pick the network up and connect onto it.

Cohen said:

Barman58 said:

Not sure if this would work on win7 - but one thing to try is to set the default gateway on the server to itself, (127.0.0.1), this should prevent the system from accessing the internet, whilst retaining access within the local subnet.

Doesn't work - it says that that address is reserved.



Cohen

OK you can obtain the same result by using the actual manual server IP address as the default gateway.

Is it just me or is "aem" confusing the living daylights out of you all too?

aem - your wrong.... you can access files on a wired network wirelessly as long as the settings are correct.

Cohen said:

aem - your wrong.... you can access files on a wired network wirelessly as long as the settings are correct.

Technically a network requires a minimun 2 pcs, If you have a server connected to a modem by wire, that to me is not a network. You may be on your ISP network but interms of your own home network, you haven't got one yet. So to be able to access your server ie connect to the shares on it, you need to connect/ping it. Right? How do you intend to do this? does your server broadcast it's IP wirelessly for your other devices to pick up?

So far we only have a server wired to the modem (i assume), and other devices which wants to connect to this server through wireless connections.

There is a network of 2 PCs connected to the broadcom router either wirelessly or wired.

the requirement is to connect a server to the existing network but to deny the server access to the network.

One example of a system that should work is this
Router IP 192.168.0.1

PC1 IP 192.168.0.2 gateway IP 192.168.0.1
PC2 IP 192.168.0.3 gateway IP 192.168.0.1

Server PC IP 192.168.0.255 Gateway IP 192.168.0.255

The two PCs may have their IP set by DHCP from the router as long as the server address is excluded from the DHCP pool

A picture is worth a thousand words. This according to Barman's instructions. Hope this helps to clarify any confusion. Just another $0.02

patwhatsthat said:

A picture is worth a thousand words. This according to Barman's instructions. Hope this helps to clarify any confusion. Just another $0.02

This is exactly what i am trying to get to.

The IPs of 192.168.x.x are part of the router's setup (Linksys IPs), they are not provided by your ISP. In other worlds, setup your router to enable DHCP, and allow your machines to auto detect IPs and you will have 192.168.x.x in your ipconfig details.

With a wireless router broadcasting the network, everything falls into place. As for restricting the server to again access to the internet. Many ways to do this, but i don't see the need to do this, why would you?

Ps I have only used static IP in a peer-to-peer networking between two PCs (with crossover cables).

The reason i want it not to access the internet is i think it is using bandwidth at night.....