HELP! Deleted network adapter IPs from a subnetted network?

rz30

rz30

rz30

Associate
Joined
5 Oct 2008
Posts
1,486
I had a crashed server so i did 2 things, disabled both onboard nics in the bios and removed a stick of memory, it turned out to be the memory so i re-enabled both nics in the bios.

After logging back on i relalised i had cleared the tcp/ip setting in the nic adapter through disabling them in the bios, actually i had to reinstall the drivers as well(thought they would be auto picked up, but this wasn't an issue).

So it windows 2000 sbs server, and it's set up so that a cat5 is connected from the router to the one of the servers NICs and another cat5 from the other server NIC to the switch. I think this is done so as to be able to use the server to monitor network traffic i.e send everything through the server.

Now the person who set this up has used 2 subnets one for the WAN side of things(192.168.1.2) and one for the LAN side of things(192.168.16.2) i found this info written down - so fact.

So as far as i can see all i have to do is hardcode both adapters, an ip, a DG, and dns ips, but i am a stuck here, i just don't have it.

I thought maybe just set the LAN adapter and ip of 192.168.16.2, 255.255.255.0, a DG of 192.168.1.1, but not sure about dns ips, i would also need an ISP dns ip if i want to get onto the net.

Any help, please, realy stuck and need it down asap.
 
Theres no real easy way for us to give you that information, its going to be specific to each network.

normally you will find the gateway is set to the first useable or last useable ip in the subnet.
do you have physical access to the router used as the gateway device, you could take the ips directly from there if you log in and query the interfaces for their ips?

do you use internal DNS servers?
if so you maybe able to port scan on your network for port 53 TCP you may find an active DNS server that way?
try using nmap, with the following parameters - nmap -p 53 <subnethere> (you can use more advanced switches on nmap, but that should suffice).
 
rz30 said:
I had a crashed server so i did 2 things, disabled both onboard nics in the bios and removed a stick of memory, it turned out to be the memory so i re-enabled both nics in the bios.

After logging back on i relalised i had cleared the tcp/ip setting in the nic adapter through disabling them in the bios, actually i had to reinstall the drivers as well(thought they would be auto picked up, but this wasn't an issue).

So it windows 2000 sbs server, and it's set up so that a cat5 is connected from the router to the one of the servers NICs and another cat5 from the other server NIC to the switch. I think this is done so as to be able to use the server to monitor network traffic i.e send everything through the server.

Now the person who set this up has used 2 subnets one for the WAN side of things(192.168.1.2) and one for the LAN side of things(192.168.16.2) i found this info written down - so fact.

So as far as i can see all i have to do is hardcode both adapters, an ip, a DG, and dns ips, but i am a stuck here, i just don't have it.

I thought maybe just set the LAN adapter and ip of 192.168.16.2, 255.255.255.0, a DG of 192.168.1.1, but not sure about dns ips, i would also need an ISP dns ip if i want to get onto the net.

Any help, please, realy stuck and need it down asap.
Click to expand...

Interesting problem. I'm no expert on SBS, in fact I've never used SBS only standard and enterprise versions of 2K/2K3, but I'll give you what advice I can.

Firstly, I would set about finding the IP address of the router that the server is connected to on the WAN Side. Since the private 192 network subnet has a default Class C subnet mask, this should make it a little easier.

Set up your WAN Side adaptor with 192.168.1.2 and 255.255.255.0. Use a tool like Angry IP Scan to scan for TCP Port 23 (Telnet) on a subnet of 192.168.1.0 /24, as I'm guessing your Router *might* allow a connection on.

Or, your router might be able to be web-managed, so again do network scan for TCP Port 80 (HTTP).

Thats the two quickest routes (no pun intended).

Failing that, its down to by hand and continual pings of 254 IP addresses to see one that responds. Ping echo response might be disabled however, so again this isn't a surefire way of finding the IP address necessary.

On the DNS side of things, isn't the SBS server itself a DNS Server?? And communicates with (possibly) your ISPs DNS Servers? I'd suggest a quick support call in this case, as I'd doubt you'd be using an Open DNS solution at business level.

As for the LAN Side adaptor, again I'm willing to bet its been setup as a fairly standard Class C Private IP address range with no subnetting. If the Switch is a decent managed switch you can use the above Angry IP scanner tip to find the IP address of the switch.

Lastly, if the Server is sat between the switch and the router, then surely something like Routing and Remote Access must have been setup so the server can act as an intermediary software router? It might be worth looking through the settings of this to tell the relevant Subnet Mask / Default gateway settings that you need.

Lastly, does SBS run some kind of 'cut-down' Active Directory? Does it have a Sites & Services mmc snap-in you can browse to discover the subnet being used for the Active Directory site? I'm guessing not, but worth a try.

I'm making a lot of assumptions here, as theres not much network detail for me to work with, but best of luck with all this.
 
I got it, i set the LAN adapter to

ip = 192.168.16.2, DG=192.168.1.1, dns = 192.168.1.1 , the routers ip is obviously 192.168.1.1 so basically send everything to the router to take care of dns.
i didn't need to set the WAN adapter anything, simple i know but had to work out the whole network setup to be able to do this.
 
You must log in or register to reply here.
Back
Top Bottom