jeffbourassa
asked on
2003 server, static IP issue
I have a win2003 server, member server in a domain, 2 network cards, and i want to set them on static IP. I can do that, but as soon as I go back into the settings it looks like it is on DHCP.
If I do ipconfig looks ok but rebooting sometimes makes it lose the static I gave it and that is a pain. I setup the server few months back and had no issues, I don't know what caused this problem now.
I haven't seen a windows server not keeping the IP settings before, not sure what to do??
Thank you,
Dan
If I do ipconfig looks ok but rebooting sometimes makes it lose the static I gave it and that is a pain. I setup the server few months back and had no issues, I don't know what caused this problem now.
I haven't seen a windows server not keeping the IP settings before, not sure what to do??
Thank you,
Dan
What IPs are you trying to use for the NICs? Are they bridged? Why do you want 2 enabled nics in member server? How many networks will this server be on? What changed?
ASKER
One NIC goes to the LAN and the other NIC to a SAN that is located in a sepparate network where there is no DHCP server.
It used to be static on SAN NIC and dynamic on LAN
Any change I do there
....if I put SAN NIC on static and go back into the settings it shows as if it is on dhcp
....if I put LAN NIC on static...the same
it simply doesn't keep the settings...although if I do a ipconfig/all it shows the addresses corectly...until I reboot and I lose connectivity
Not sure where to start .... I would avoid reinstalling from scratch if possible
It used to be static on SAN NIC and dynamic on LAN
Any change I do there
....if I put SAN NIC on static and go back into the settings it shows as if it is on dhcp
....if I put LAN NIC on static...the same
it simply doesn't keep the settings...although if I do a ipconfig/all it shows the addresses corectly...until I reboot and I lose connectivity
Not sure where to start .... I would avoid reinstalling from scratch if possible
ASKER
...and it worked just fine until ercently (I am certain), I don't know exactly when this problem appeared, I noticed it as I wanted to change the IP on the SAN NIC
This is a strange result to have IP addresses not stick when looking at the windows GUI.
Just for the sake of troubleshooting run through these steps:
1. Disable SAN nic in control panel/network connections
2. Assign or make sure the LAN nic is showing and holding the correct IP (eg. 192.168.0.10)
3. Make sure clients comm with server and server comm with clients and internet.
If that works then you can troubleshoot the SAN nic and SAN connectivity.
I would like to know how you are using your SAN. You must be creating the shares on the server and connecting your clients to the SAN via the server shares, true or false?
If that is how you are sharing the SAN disks then try to use a different network for the SAN nic. (eg. 192.168.1.10)
Make sure the nic on the SAN device is using something like 192.168.1.11.
Also something I just though about that isn't so important; are you using a switch for the SAN or cross over cable?
Just for the sake of troubleshooting run through these steps:
1. Disable SAN nic in control panel/network connections
2. Assign or make sure the LAN nic is showing and holding the correct IP (eg. 192.168.0.10)
3. Make sure clients comm with server and server comm with clients and internet.
If that works then you can troubleshoot the SAN nic and SAN connectivity.
I would like to know how you are using your SAN. You must be creating the shares on the server and connecting your clients to the SAN via the server shares, true or false?
If that is how you are sharing the SAN disks then try to use a different network for the SAN nic. (eg. 192.168.1.10)
Make sure the nic on the SAN device is using something like 192.168.1.11.
Also something I just though about that isn't so important; are you using a switch for the SAN or cross over cable?
ASKER
This is a strange result to have IP addresses not stick when looking at the windows GUI.
---YES, it is strange
Just for the sake of troubleshooting run through these steps:
1. Disable SAN nic in control panel/network connections
2. Assign or make sure the LAN nic is showing and holding the correct IP (eg. 192.168.0.10)
3. Make sure clients comm with server and server comm with clients and internet.
If that works then you can troubleshoot the SAN nic and SAN connectivity.
I would like to know how you are using your SAN. You must be creating the shares on the server and connecting your clients to the SAN via the server shares, true or false?
--- The SAN is iSCSI, completely different network and different netwrok address. The server has DISKS from the SAN and exopeses those disks to clients (by sharing folders on those disks)
If that is how you are sharing the SAN disks then try to use a different network for the SAN nic. (eg. 192.168.1.10)
---The network address is completely different, of course
Make sure the nic on the SAN device is using something like 192.168.1.11.
Also something I just though about that isn't so important; are you using a switch for the SAN or cross over cable?
--- YES, I have a swithch as several servers are connected the same way to the SAN as this one
---YES, it is strange
Just for the sake of troubleshooting run through these steps:
1. Disable SAN nic in control panel/network connections
2. Assign or make sure the LAN nic is showing and holding the correct IP (eg. 192.168.0.10)
3. Make sure clients comm with server and server comm with clients and internet.
If that works then you can troubleshoot the SAN nic and SAN connectivity.
I would like to know how you are using your SAN. You must be creating the shares on the server and connecting your clients to the SAN via the server shares, true or false?
--- The SAN is iSCSI, completely different network and different netwrok address. The server has DISKS from the SAN and exopeses those disks to clients (by sharing folders on those disks)
If that is how you are sharing the SAN disks then try to use a different network for the SAN nic. (eg. 192.168.1.10)
---The network address is completely different, of course
Make sure the nic on the SAN device is using something like 192.168.1.11.
Also something I just though about that isn't so important; are you using a switch for the SAN or cross over cable?
--- YES, I have a swithch as several servers are connected the same way to the SAN as this one
ASKER
1- disabled the SAN NIC
2- setup LAN NIC on static
3- ipconfig/all shows it correctly (on static)
4- went back into LAN NIC settings (shows like dynamic!!!!!)
2- setup LAN NIC on static
3- ipconfig/all shows it correctly (on static)
4- went back into LAN NIC settings (shows like dynamic!!!!!)
ASKER
5- enabled SAN NIC (that used to be on static before disabling according to ipconfig but not to GUI)
6- ipconfig shows SAN NIC 169.x.x.x address
7- went into settings, put it on manual
8- ipconfig looks right and I have SAN conenctivity
9- went into SAN NIC settings and it shows like on dynamic
6- ipconfig shows SAN NIC 169.x.x.x address
7- went into settings, put it on manual
8- ipconfig looks right and I have SAN conenctivity
9- went into SAN NIC settings and it shows like on dynamic
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do they act like dynamic addresses? If you ping the LAN nic from workstation do you get a response? At what point does the ipconfig /all command show the default address 169.254.x.x?
Have you tried reinstalling NIC from device manager and/or reinstalling network protocols and services from the server?
Have you tried reinstalling NIC from device manager and/or reinstalling network protocols and services from the server?