Robert McLaws: Windows Edition

Blogging about Windows since before Vista became a bad word

I Need Some Windows Server 2008 Assistance

So I've got brand new servers running Windows Server 2008 x64, and I'm getting ready to get my infrastructure moved over, but I'm definitely having some networking related issues that I could use some help on.

Basically, my server has two NICs, one public and one private. The problem is, both cards are showing up as "Unidentified Network", which means that WS2008 is lumping them together into the same firewall profile. I need to know if it is possible to manually set a network's name (not the connection name, I know how to do that), so that I can separate the cards. Alternatively, I need to know how to manually assign a network connection to a firewall profile, even if the network isn't identified.

If someone can please help me with those two things, I might be able to take advantage of these AMD quad-core boxes with 6GB RAM a piece that I'm running now. Thanks!

PostTypeIcon
21,337 Views

Comments

  • Joseph said:

    Robert - I don't know that you can have 2 different Firewall profiles, one for each connection without something like ISA, but if you want one connection to have Firewall and one to not have it, then it is in the Advanced tab of the Windows Firewall dialog from the link in Network Connections.  Hope that helps.

    August 16, 2007 8:42 AM
  • bigred said:

    I've only used ISA to make my life easier.  Maybe I was too lazy to do it your way, but I haven't worked with ws08 yet.  Sorry.

    August 16, 2007 12:01 PM
  • Tony Gulino said:

    Hey Robert,

    Joseph has a good solution up top, but I came up with another solution when for some reason Vista was re-evaluating the crossover connection between my desktop and tablet. I went into Windows Firewall with Advanced Security (I assume it's in WS2008 as well) and under Inbound Rules, add a New Rule, make sure all the "allow" options/checkboxes are on, and under Scope, choose Local/Remote IP address to be in the 192.168.0.1-192.168.0.255 range (or whatever range your private network uses). You might have to do one with Outbound Rules too.

    I set that rule up on both my desktop and tablet, so even if it says Unidentified PUBLIC network, as long as the IP address is in that range, it will allow network connections. Now keep in mind my systems are physically-secured anytime I'm not around them. As for your specific situation with your server, this might not be the best solution, but give it a try.

    August 16, 2007 12:45 PM
  • Can you send the output of your ipconfig /all to me  so we can identify why the network is coming up as unidentified? There are ways to set the network name through Group policy, but It would be helpful to see why they arent being detected correctly. my email address is tparks@<guesswhattoputhere>.com

    -Tripp

    August 16, 2007 1:28 PM
  • I Need Some Windows Server 2008 Assistance - Robert McLaws: Windows Edition

    September 16, 2014 3:46 AM