which cable goes where?

I had set up routing and remote access with the wizard in Windows Server
2003. Somehow the server doesn't call the nic cards by their actual
manufacturer. When I unplugged the cables I forgot which one goes where.
How do I make sure which cable goes into the lan and which one connects to
the internet?

Daniel

"Daniel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I had set up routing and remote access with the wizard in Windows Server
> 2003. Somehow the server doesn't call the nic cards by their actual
> manufacturer. When I unplugged the cables I forgot which one goes where.
> How do I make sure which cable goes into the lan and which one connects to
> the internet?
>
> Daniel
>
>

- Plug the internal LAN cable into one of the adapters.
- Check the status of both adapters. One of them will
show that it has a cable connected.
- Check the IP address of this adapter. If the subnet
is the subnet of the internal network then the cable
is in the correct socket.

Then go to Control Panel -> Network Connections. R-click each connection
and Rename it to something more appropriate.


"Pegasus (MVP)" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Daniel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I had set up routing and remote access with the wizard in Windows Server
>> 2003. Somehow the server doesn't call the nic cards by their actual
>> manufacturer. When I unplugged the cables I forgot which one goes where.
>> How do I make sure which cable goes into the lan and which one connects
>> to
>> the internet?
>>
>> Daniel
>>
>>
>
> - Plug the internal LAN cable into one of the adapters.
> - Check the status of both adapters. One of them will
> show that it has a cable connected.
> - Check the IP address of this adapter. If the subnet
> is the subnet of the internal network then the cable
> is in the correct socket.
>
>

Im a newbee, but wouldnt recomend renaming or manually adjusting the NICs!

Use the "Internet-Connection" WIZARD, it should rename 1 of the adapters
(internal intranet) to "server local area connection" or similar,
and leaves the external (web) NIC as "Local Area Connection"

If the wizard fails you will need to reinstall SBS, the documentation does
tell you to have all the hardware in place first. I would make sure the NICs
are Windows self install compliant, ie dont require manufacturer drivers!

JD

"Dave Nickason [SBS MVP]" <(E-Mail Removed)> wrote in message
news:e$(E-Mail Removed)...
> Then go to Control Panel -> Network Connections. R-click each connection
> and Rename it to something more appropriate.
>
>
> "Pegasus (MVP)" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>> "Daniel" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> I had set up routing and remote access with the wizard in Windows Server
>>> 2003. Somehow the server doesn't call the nic cards by their actual
>>> manufacturer. When I unplugged the cables I forgot which one goes
>>> where.
>>> How do I make sure which cable goes into the lan and which one connects
>>> to
>>> the internet?
>>>
>>> Daniel
>>>
>>>
>>
>> - Plug the internal LAN cable into one of the adapters.
>> - Check the status of both adapters. One of them will
>> show that it has a cable connected.
>> - Check the IP address of this adapter. If the subnet
>> is the subnet of the internal network then the cable
>> is in the correct socket.
>>
>>
>
>

What is wrong with renaming? It takes about a second, does not require a
reboot, and you'd never have to reinstall anything if anything goes wrong...
and the only way something could go wrong is if you pick a bad name at which
point it'll probably just tell you to pick another or just block the name
change and complain.

"jd" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Im a newbee, but wouldnt recomend renaming or manually adjusting the NICs!
>
> Use the "Internet-Connection" WIZARD, it should rename 1 of the adapters
> (internal intranet) to "server local area connection" or similar,
> and leaves the external (web) NIC as "Local Area Connection"
>
> If the wizard fails you will need to reinstall SBS, the documentation does
> tell you to have all the hardware in place first. I would make sure the
> NICs are Windows self install compliant, ie dont require manufacturer
> drivers!
>
> JD
>
> "Dave Nickason [SBS MVP]" <(E-Mail Removed)> wrote in
> message news:e$(E-Mail Removed)...
>> Then go to Control Panel -> Network Connections. R-click each connection
>> and Rename it to something more appropriate.
>>
>>
>> "Pegasus (MVP)" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>
>>> "Daniel" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> I had set up routing and remote access with the wizard in Windows
>>>> Server
>>>> 2003. Somehow the server doesn't call the nic cards by their actual
>>>> manufacturer. When I unplugged the cables I forgot which one goes
>>>> where.
>>>> How do I make sure which cable goes into the lan and which one connects
>>>> to
>>>> the internet?
>>>>
>>>> Daniel
>>>>
>>>>
>>>
>>> - Plug the internal LAN cable into one of the adapters.
>>> - Check the status of both adapters. One of them will
>>> show that it has a cable connected.
>>> - Check the IP address of this adapter. If the subnet
>>> is the subnet of the internal network then the cable
>>> is in the correct socket.
>>>
>>>
>>
>>
>
>

Last time i messed with the NIC names and IP addresses I had to do a clean
install.

"Bob Hetzel" <(E-Mail Removed)> wrote in message
news:draoka$jlg$(E-Mail Removed)...
> What is wrong with renaming? It takes about a second, does not require a
> reboot, and you'd never have to reinstall anything if anything goes
> wrong... and the only way something could go wrong is if you pick a bad
> name at which point it'll probably just tell you to pick another or just
> block the name change and complain.
>
> "jd" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Im a newbee, but wouldnt recomend renaming or manually adjusting the
>> NICs!
>>
>> Use the "Internet-Connection" WIZARD, it should rename 1 of the adapters
>> (internal intranet) to "server local area connection" or similar,
>> and leaves the external (web) NIC as "Local Area Connection"
>>
>> If the wizard fails you will need to reinstall SBS, the documentation
>> does tell you to have all the hardware in place first. I would make sure
>> the NICs are Windows self install compliant, ie dont require manufacturer
>> drivers!
>>
>> JD
>>
>> "Dave Nickason [SBS MVP]" <(E-Mail Removed)> wrote in
>> message news:e$(E-Mail Removed)...
>>> Then go to Control Panel -> Network Connections. R-click each
>>> connection and Rename it to something more appropriate.
>>>
>>>
>>> "Pegasus (MVP)" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>
>>>> "Daniel" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> I had set up routing and remote access with the wizard in Windows
>>>>> Server
>>>>> 2003. Somehow the server doesn't call the nic cards by their actual
>>>>> manufacturer. When I unplugged the cables I forgot which one goes
>>>>> where.
>>>>> How do I make sure which cable goes into the lan and which one
>>>>> connects to
>>>>> the internet?
>>>>>
>>>>> Daniel
>>>>>
>>>>>
>>>>
>>>> - Plug the internal LAN cable into one of the adapters.
>>>> - Check the status of both adapters. One of them will
>>>> show that it has a cable connected.
>>>> - Check the IP address of this adapter. If the subnet
>>>> is the subnet of the internal network then the cable
>>>> is in the correct socket.
>>>>
>>>>
>>>
>>>
>>
>>
>
>

I agree with Bob. I don't see how renaming a network connection can be
negative in any way. I do it all the time on servers with more than one
NIC. I will even do it on production critical systems during the day.
It can get really confusing (without renaming connections) when you got
a server with teamed NICs and heartbeats and backup connections.

Although I could be wrong here, I wouldn't be afriad to rename the
connections.

Bob Hetzel wrote:
> What is wrong with renaming? It takes about a second, does not require a
> reboot, and you'd never have to reinstall anything if anything goes wrong...
> and the only way something could go wrong is if you pick a bad name at which
> point it'll probably just tell you to pick another or just block the name
> change and complain.
>
> "jd" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Im a newbee, but wouldnt recomend renaming or manually adjusting the NICs!
> >
> > Use the "Internet-Connection" WIZARD, it should rename 1 of the adapters
> > (internal intranet) to "server local area connection" or similar,
> > and leaves the external (web) NIC as "Local Area Connection"
> >
> > If the wizard fails you will need to reinstall SBS, the documentation does
> > tell you to have all the hardware in place first. I would make sure the
> > NICs are Windows self install compliant, ie dont require manufacturer
> > drivers!
> >
> > JD
> >
> > "Dave Nickason [SBS MVP]" <(E-Mail Removed)> wrote in
> > message news:e$(E-Mail Removed)...
> >> Then go to Control Panel -> Network Connections. R-click each connection
> >> and Rename it to something more appropriate.
> >>
> >>
> >> "Pegasus (MVP)" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >>>
> >>> "Daniel" <(E-Mail Removed)> wrote in message
> >>> news:(E-Mail Removed)...
> >>>> I had set up routing and remote access with the wizard in Windows
> >>>> Server
> >>>> 2003. Somehow the server doesn't call the nic cards by their actual
> >>>> manufacturer. When I unplugged the cables I forgot which one goes
> >>>> where.
> >>>> How do I make sure which cable goes into the lan and which one connects
> >>>> to
> >>>> the internet?
> >>>>
> >>>> Daniel
> >>>>
> >>>>
> >>>
> >>> - Plug the internal LAN cable into one of the adapters.
> >>> - Check the status of both adapters. One of them will
> >>> show that it has a cable connected.
> >>> - Check the IP address of this adapter. If the subnet
> >>> is the subnet of the internal network then the cable
> >>> is in the correct socket.
> >>>
> >>>
> >>
> >>
> >
> >