Windows 2000 Server in 2 networks

[Peter]

We are running a Windows 2000 Server in our network.

However, we would like to set up another small testing
environment by using that Server with 2 Windows 2000
workstations. They are connected via a hub AND we will
switch the cable if we change the Server from the network
to the testing network.

We would like to know for the LAN, we have assigned the
address 192.16.16.100 to that Server. Can we assign
another IP address like 192.18.18.100 to that Server for
the small testing network ? How does the server knows
which IP address to use ?

Thanks

 

[Doug Sherman [MVP]]

Yes, you can assign a second IP address to the existing adapter. However,
NetBT (NetBIOS) will only function on the first bound IP address. A more
conventional approaoch would be to install a second adapter in the server
and connect it to both networks.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Peter]

I am new to networking and would like to know what is the
consequence if NetBIOS doesn't work with the 2nd bound
address ?

Thanks

 

[Doug Sherman [MVP]]

The biggest consequence would be browsing - the server would only announce
its name and resources under the 1st IP address. But you should still be
able to connect to it using \\<2ndIPaddress>. If instead you had 2 network
adapters, you could assign 192.16.16.100 to one and 192.18.18.100 to the
other and be connected to both networks at the same time.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Peter]

Dear Doug,

Thank you for your advice.

I would like to know to like no browsing, does it mean
that we are not able to see the Server in Network
Negibourhood EVEN THOUGH there the Browser Service is
still enabled in other machines in that network ?

Besides, does it mean that we can still acess it via UNC
connection ?

Thanks

 

[Doug Sherman [MVP]]

You might well be able to see an icon for the machine in My Network Places,
but the icon/name would resolve to 192.16.16.100 and machines on a
192.18.18.x subnet would not know where to send packets in order to connect
to it. You could connect to it by IP address: \\192.18.18.100. Or you
could create an lmhosts file on the other machines that maps 192.18.18.100
to the machine's name, then you should be able to connect by \\machinename.
See:

http://www.microsoft.com/resources/...0/server/reskit/en-us/prork/prcc_tcp_hgwc.asp

and

http://www.microsoft.com/resources/.../professional/reskit/en-us/part4/proch22.mspx

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP