Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

W2K server can't talk on network if IP is static

Status
Not open for further replies.

lksixt

IS-IT--Management
Apr 26, 2002
44
US
Hi.. our mail server is assigned a static IP of 10.0.18.4. Everything was working fine, until our air conditioning unit stopped and the server room overheated. I shut everything down, after a/c was fixed i booted up all the servers and our mail server couldn't communicate to anyone, nor could anybody else see it. Here's the wierd part.. if i don't set a static ip, then it can ping in and out... but that won't do me any good for a mail server...

i don't know if the heat could have anything to do with any of this... i'm very confused.

Is there anybody out there that could help me?

 
The obvious first question is, after the mass reboot, has another device somehow grabbed the mailserver's IP? Can you still ping that IP when the mail server is set to something else?
 
Thanks, I hadn't thought of that... but no I can't.
The other really strange this is this... if i use the static IP, i cannot bring up a web page.. if i let DHCP assign one, then I can get out to the internet.

What is up with that?
 
ok... check this out. i have two domain controllers, one on our academic vlan and one on our administrative vlan. The mail server is on the academic, when i let DHCP assign an address it gets on from the admin pool, if i assign it any address on the academic vlan, not only the 10.0.18.4, it can't connect to the internet or be seen....
 
Sounds like maybe your missing the gateway.

do an ipconfig /all and compare the ip settings when you use static and dhcp configuration.

-Danny
dan@snoboarder.net






 
Almost sounds like it just got plugged into the wrong port on the switch. But if all you did was turn power off and on... how could that happen? Recheck the switch and make sure that port it's on is still on the correct vlan.
 
good idea.... different gateways are used. If I let DCHP assign the IP, it comes from my administrative vlan10.0.15.125... then the gateway is also on that vlan...

if i assign ip from the academic vlan... 10.0.18.#, i use 10.0.18.1 as the gateway.

but i have another server, the student server that is 10.0.18.2 using 10.0.18.1 as the gateway and it is seen just fine..

If I assign any ip address within the academic range (that isn't already taken I seem to die)

I'm still on a learning curve here and my network consultant is out of town... thanks for you help
 
YOU ARE RIGHT! I checked my switch and the port is now on the admin vlan... it used to be, then when we installed the new mail server a couple of weeks ago, we changed that to the academic vlan

could powering off/on the switch have set things back?
 

Gosh whos switch are you using?? A brown-out or power outage should NOT have switched the managment vlan around. However someone playing with SNMP could change the configuration and you would never know until too late <G>

I used radius for telnet authentication, and the snmp comm strings have too cryptic to figure out :)

Hope that helps.
Cheers.

NTS ! /
 
it's a cisco switch, i guess when i changed the port setting, i didn't save it to a file that it would use at power up... i thought when you reconfigured a port it was automatically saved.

Does that make sense?
 
It makes some sense, there's a running config and a (I forget the name) &quot;saved&quot; config in the Cisco hardware I've dealt with. You adjusted the running config, but the hardware reverts to the &quot;saved&quot; config on bootup. I'm sure someone smarter with Cisco could clarify or correct this.
-Steve
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top