Hi,
I'm helping out a friend with a sbs2003.
They rebooted the server and lost all the computers connected to it.
I read the the IP address was supported to be private, and it was set as obtain automactly.
the DNS was set as 192.168.2.10
Am I on the right track?
What should I use as an IP (If I am?)
All they really do with this servers is share data/printers.
Thanks In Advance
Joe
I'm helping out a friend with a sbs2003.
They rebooted the server and lost all the computers connected to it.
I read the the IP address was supported to be private, and it was set as obtain automactly.
the DNS was set as 192.168.2.10
Am I on the right track?
What should I use as an IP (If I am?)
All they really do with this servers is share data/printers.
Thanks In Advance
Joe
-
In general, servers should have a statically-set IP address. Certainly DHCP *should* work, but this is one case where it may not.
Is the server on 192.168.2.10 also a domain controller or other windows server providing DHCP? -
-
Here's where I get lost...
This is the way the office is set up.
Three pc's and the one server.
DSL service is from verizon.
Dsl modem goes into hub,
PC's go into hub.
Server goes into hub, but is setup only to share files/printers with the 3 pc's.
The pc's get Internet access thru the DSL.
So is it safe to say, that if I give the network card 192.168.2.10 as it's adresss, the add a computer , the pc will now see the shared drives on the server?
I know.. it should be all reconfigured...
Thnaks -
-
"I know.. it should be all reconfigured... "
Indeed. What you _should_ do is isolate DHCP via DSL so that it's not available. Put something between it and the private nework. (I would suggest IPCop - great firewall, etc.)
In the Windows 2000+ world, DHCP really needs to be "authorized" in your active directory structure for extra security as well. I would suggest the server become 192.168.1.1/24, with DHCP service providing a scope that has 192.168.1.10 - 20, with the IPCop firewall as 192.168.1.254. Make 254 your default gateway in the DHCP scope. You can also run DNS on the server, and allow dynamic updates. Thus, all systems on the LAN side will be aware of host/IP for one another at all times. -
-
Thanks for all the advice,
I can't get at the server until Saturday AM.
I don't think I expained it right.
I think the server is "kinda" setup like file sharing a PC.
It doesn't do DHCP, the Verizon router does it.
To get it up quick, do you think
if I set the IP as 192.168.2.10, like the DNS, and now that I think about it
I think that was the address, I can add computers and let the PC get at there
files?
Thanks Again
-
-
If you set the IP to 192.168.2.10, first make sure the Verizon router's DHCP server isn't going to give that same IP address out to another computer.
If you're using all Windows boxes with Windows file sharing on a simple LAN you can probably get away without using DNS at all for your internal systems - NetBIOS over TCP/IP will take care of local name resolution without it. -
-
Hi Ivan,
Thanks for the advice.
You know, guys who write code shouldn't be playing with servers.. :)
So, if I understand you correctly:
Check the routher, see if it's doing DHCP, if yes, check the address range, make sure 192.168.2.10 is out of range.
Give the Network card(only one) 192.168.2.10
Do the add a computer "thing" from the server,, and file sharing should be back?
I can't get at it until tomorrow, but I think it was "obtain automatically", so it was getting it from the router?
?... Should I go into services and make sure any DNS services are shutoff, or does it matter?
If so, do you know the names of them or will I recognize them?
Thanks Again..
Joe
-
-
-
-
-
