cryingvalor

- hey guys i want to change the ip address of our network but we have DC in our network... how do i properly change it without causing problems in our network...

SafeFromSites

What is the purpose of the IP change? servers allow you to assign multiple IPs to the same interface, so you could just add it. Re-point every one, and then remove the old IP, and just make sure every thing gets updated correctly in the DNS.

cryingvalor

-well our network will be connecting to a 1 computer installed with win03 and 2 NICs our neighboring office will also connect to this computer for file sharing thats why it has 2 NICs, the problem is that we have the same IP addressing thats why 1 of us must change its network ip address and that would be us
-im not quite familiar with this...how do you implement this one...

SafeFromSites

to assign a additional IP you go into the connection properties, and its under advanced. Second, you say you have 2 NICs because you want the other network to use the server also for file sharing, You don't need two NICs to connect the two networks, they could all be in the same IP range. if the other network is off site, you can use a VPN , if its literally right next door you should only need to connect the two switches together. Do you not want the two networks to see each other? I may be interpreting your scenario wrong, but I think there is a better way to achieve your goal.

cryingvalor

- got this one ....so whats the benefit of having 2 ip address on a single NIC?
-yes, actually we just want file sharing...
-this is what im looking for

SafeFromSites

ok, so the reason for being able to put multiple IPs on one NIC is mainly becasue of why you would want multiple NICs. For instance, redundancy, doubling bandwidth, using the server as a router, using the server as a firewall.... for one personal example, I have a server on the internet, its NIC has multiple IPs, some IPs are for differnet web sites, and some IPs are for internal use only, as in remote control of the server.

For you and your network, I need a little more topology, so that I can help you design the a better way of layign it out. Such as, what types of switches are you running, smart, not smart, do they support VLAN, or trunking. are both networks with in cabling distance of each other, or are they to be connected via a interntet connection. how many network devices are we talking about ? and also, what is the make of your NICs. And finaly just so that I am clear, will both networks see different shared folders, but be authenticated by the same server?

cryingvalor

- well our switches are just ordinary DLINK and EDIMAX switches... and doesnt support those funtionalites...
- yes
- also a consideration if the setup we are working will not work or if its a bad network design...
- combining our network and our neighbor about 30 computers...
- do you mean maker?... well most of our NICs are buil-in realtek lan cards....and others are edimax....
- yes...

SafeFromSites

Ok, so, what we have is a no frills network, so I will try to make this simple.

The way I would do this goes like this. Since we are only dealing with 30 computers, and I am guessing there are a few network printers in the mix also , so all total, not much more that 50 total devices, I would go with the same IP scheme for both networks.

So leave the server IP just the way it is, since you said both networks already have the same scheme going. Second, I would link both switches together. I don’t know the age of your equipment, but you might be able to use a uplink port on each if available, if not just use a cross over cable and use any port on both switches, you might be able to get away with a standard cable, the new switches support auto crossover. You don’t want to run the traffic thru the server(2 NIC), because then all traffic, including, internet, printing… would be going thru it and slowing it down, for no particularly good reason.

To separate the two networks, I would create two groups in the Active directory. assign the correct users to the groups and assign the permissions to the folders by group. That way, all the shares can be seen by the admin from either side, but only those who belong to the correct group will be able to access the folders that they are suppose to. Having both sides connected this way means that you will only need one internet connection, however if you have two, and need two for bandwidth there are a couple way you can combine the connections using special routers. Some are very affordable, some are expensive, but more capable. Also this arrangement will allow sharing of printers on each side(can be a nice option).

If both of the server NICs were the same I would have suggested teaming them together, but since they are not, don’t worry about it. Two NICs can cause trouble if not setup right, so I would say worry about that last. Also a VLAN would have been fun, you ought to look it up some time, but that is how you can physically have two networks on the same switch, and not able to see each other, but able to see the same server. Trunking, is how you double bandwidth by using two NICs.

Also, you will need to make sure that there is only one device handing out DHCP. Personally I would suggest the server,(makes for better DNS updates) but if you are not comfortable with that, that is fine, you can continue to use the router/modem, or whatever you currently have setup.

SafeFromSites

if you want to make the two networks completely separate, then that would involve a bit of a different scheme, but I can lay that out for you also if you like.

cryingvalor

- yes please

SafeFromSites

ok, ugg, I need to look up and verify a couple things first, ill be back,

a VLAN would have made this real easy

SafeFromSites

thinking back, I recall that even if you use two differnt NICs with different IP schemes the server will still link the two networks

cryingvalor

- so both network can access each other...

SafeFromSites

thats what I remember, but I need to verify, I am pretty sure that can be gotten around using routing and remote access, but I need to look it up

cryingvalor

- i also tried using routing and remote access but no such luck im not quite familiar with this actually so im not sure if im doing it right...

SafeFromSites

well I am not finding what I want, so here is are my thoughts of the moment, you can do two NICs but you cannot have two gateways, it will cause problems, you can do a different IP range to separate the network, but your DNS will list all the IPs associated with the server , in a order, so one network will have no issue seeing the server, the other network, will probably try to connect to the IP that it cant see. so you really want to have the two networks visible thru the server, and then set rules for what can cross over and from where. and thats where I believe R&RA needs to come to play, basically create some routing rules. that said, I am not sure you want to get into that. That and I am not the best at routing. option two is a VLAN, but that would require different hardware, its basically the same as the routing game, but way easier to setup. option three, well there must be one, but I need to think about what it could be, or some one else chime in with there thoughts. and of coarse plan A , but you don't seem to want the two networks to see each other on any level for whatever reason.

SafeFromSites

did a bit of looking around, your best bet is to buy a VLAN switch. which one to get is something you should contact the switch maker about. I have had good luck with D-Links business switches, for cheap solutions, but either way talk to them, they will help you dial in a answer.

cryingvalor

-ok, thanks so much for your help...