TMG RC: Getting Started Wizard fails in Configure Network Settings
I installed the TMG RC on a fresh install of Windows 2008 R2 Std. (joined to the domain) last night. The setup went flawlessly (love the prerequisites handler!). However, I cannot get past the Configure Network Settings phase of the Getting Started Wizard. I selected the "3-leg perimeter" option.
The network setup looks something like this:
LAN
IP: 192.168.1.254
Subnet mask: 255.255.255.0
Default gateway: (blank)
DNS: 192.168.1.200
Internet:
IP: (static public IP address)
Subnet mask: 255.255.255.248
Gateway: (gateway for that subnet)
DNS: (ISP DNS)
DMZ
IP: 192.168.100.254
Subnet mask: 255.255.255.0
Default gateway: (blank)
DNS: (blank, also tried 192.168.1.200)
When I click Finish at the end of the setup, it gives a variety of errors (unfortunately, it doesn't list which NIC is the "specified network adapter"):
0xC004045E: The list of DNS addresses for the specified network adapter includes duplicates.
0xC004045C: The list of IP addresses for the specified network adapter includes duplicates.
Or 0x80004005: Unspecified error.
I've tried quite a few things--backing out and setting up the NIC properties directly then re-running the Configure Network Settings wizard, uninstalling TMG and reinstalling and re-running the wizard, and starting from scratch with a complete reinstall of Windows, TMG, and re-running the wizard. Any thoughts?
Thanks!
Ryan
Answers
- Anyone here? Echo... echo....
Well, it appears I've found a resolution, though I did not see (so far) any documentation indicating this would be necessary. When I was going through the Configure Network Settings wizard, I had only one of the NICs connected. My plan was to configure all the NICs offline, then connect them later. I didn't want to have an IP conflict, plus it would be nice to keep the existing ISA box active before putting this in its place with nearly identical settings.
I saw some very erratic activity in the TMG console around IP addresses on the Network Interfaces tab. No matter how I configured these on the NICs themselves (offline), the console showed two IP addresses--the one I assigned, and another 169.x.x.x address. I attempted to apply these settings, but it would not allow me to do so--it would give the duplicate IP addresses error. If I set it to DHCP instead (just to see what would happen) and tried to apply the changes, it would give an "Unspecified error." I tried quite a variety of combinations between changing the IP settings through the Windows GUI and through the TMG console, which allowed me to see the errors specific to the network adapter. The Configure Network Settings gives the same error message, but does not tell you for which network adapter... and since it would appear this wizard needs to be dealt with before going into the console, I was stuck at this point for quite awhile.
At this point, I tried plugging in the one network cable to different adapters, and noticed that I succeeded with the configuration changes for that particular adapter. Then I grabbed a small switch and simply plugged in all the NICs, configured them and applied the changes. Sure enough, that works.
I would suggest that this be addressed before RTM, but if it's in the documentation that all NICs need to be connected to a network, that's my fault. It's simple enough to plug them into a dummy switch, but to me, it seems that should not be necessary.
Hope this helps someone else!
Ryan- Marked As Answer byNick Gu - MSFTMSFT, ModeratorThursday, October 29, 2009 6:52 AM
All Replies
- Anyone here? Echo... echo....
Well, it appears I've found a resolution, though I did not see (so far) any documentation indicating this would be necessary. When I was going through the Configure Network Settings wizard, I had only one of the NICs connected. My plan was to configure all the NICs offline, then connect them later. I didn't want to have an IP conflict, plus it would be nice to keep the existing ISA box active before putting this in its place with nearly identical settings.
I saw some very erratic activity in the TMG console around IP addresses on the Network Interfaces tab. No matter how I configured these on the NICs themselves (offline), the console showed two IP addresses--the one I assigned, and another 169.x.x.x address. I attempted to apply these settings, but it would not allow me to do so--it would give the duplicate IP addresses error. If I set it to DHCP instead (just to see what would happen) and tried to apply the changes, it would give an "Unspecified error." I tried quite a variety of combinations between changing the IP settings through the Windows GUI and through the TMG console, which allowed me to see the errors specific to the network adapter. The Configure Network Settings gives the same error message, but does not tell you for which network adapter... and since it would appear this wizard needs to be dealt with before going into the console, I was stuck at this point for quite awhile.
At this point, I tried plugging in the one network cable to different adapters, and noticed that I succeeded with the configuration changes for that particular adapter. Then I grabbed a small switch and simply plugged in all the NICs, configured them and applied the changes. Sure enough, that works.
I would suggest that this be addressed before RTM, but if it's in the documentation that all NICs need to be connected to a network, that's my fault. It's simple enough to plug them into a dummy switch, but to me, it seems that should not be necessary.
Hope this helps someone else!
Ryan- Marked As Answer byNick Gu - MSFTMSFT, ModeratorThursday, October 29, 2009 6:52 AM
- Ryan, thanks for saving me some frustration this morning!
Zach
