Wired/Wireless NICs

I have a Windows Sever 2003 machine that I am unable to get the wired NIC to
work properly. I first installed the NIC, then installed Server 2k3, then
installed the NIC drivers. The card is able to connect to my network and is
able to connect to my router. However, I am unable to get the card to access
the internet. I later installed a wireless NIC adapter and it is able to get
on the network and the internet. The wired card is using the IP address
192.168.0.12 and the wireless NIC is using 192.168.0.13. I have experienced
this problem before under WinXP and the solution I've always used was to
simply bridge the connection and then both connections were fully
functional... however, I have yet to discover how to bridge a connection in
Server 2003.

Basically, I am trying to get the wired NIC to be able to connect to the
internet without the need for the wireless NIC.

Any advice is appreciated.

Thanks,
LargeNostril

Disable the wireless NIC then check connectivity between
the W2k3 server and the default gateway e.g., ping. Next
try to ping the external DNS server. Do you get a response?
How about opening a dos prompt and running nslookup
www.msn.com? Do you get a response from the DNS
server?

"LargeNostril" <(E-Mail Removed)> wrote in message
news:
> I have a Windows Sever 2003 machine that I am unable to get the wired
NIC to
> work properly. I first installed the NIC, then installed Server 2k3,
then
> installed the NIC drivers. The card is able to connect to my network
and is
> able to connect to my router. However, I am unable to get the card to
access
> the internet. I later installed a wireless NIC adapter and it is able
to get
> on the network and the internet. The wired card is using the IP
address
> 192.168.0.12 and the wireless NIC is using 192.168.0.13. I have
experienced
> this problem before under WinXP and the solution I've always used was
to
> simply bridge the connection and then both connections were fully
> functional... however, I have yet to discover how to bridge a
connection in
> Server 2003.
>
> Basically, I am trying to get the wired NIC to be able to connect to
the
> internet without the need for the wireless NIC.
>
> Any advice is appreciated.
>
> Thanks,
> LargeNostril

Thanks for the feedback.

I have tried as you suggested and I do get a response when I ping anything
on my local network, including my router (192.168.0.1). However, I get a
timeout when I ping anything else. As for nslookup, I get a timeout as well.

However, with my wireless NIC enabled and wired NIC disabled, I get
responses from both the ping and nslookup.

And I also tried the wired NIC in 3 other computers (WinXP, RedHat
Enterprise, Win2000) and it works fine in those configurations.

Thanks,
LargeNostril

You have ruled out the NIC but you'll need to check
cable / routing.

"LargeNostril" <(E-Mail Removed)> wrote in message
news:
> Thanks for the feedback.
>
> I have tried as you suggested and I do get a response when I ping
anything
> on my local network, including my router (192.168.0.1). However, I
get a
> timeout when I ping anything else. As for nslookup, I get a timeout
as well.
>
> However, with my wireless NIC enabled and wired NIC disabled, I get
> responses from both the ping and nslookup.
>
> And I also tried the wired NIC in 3 other computers (WinXP, RedHat
> Enterprise, Win2000) and it works fine in those configurations.
>

What would I need to check regarding routing? I have already tested various
cat5/e cables and have tried several other NICs/computers on the router port
my Server 2003 machine is connection to and I get the same results. What
kind of settings should I be looking for in my router?

Also, could this issue have anything due with my installation being the
evaluation version?

Sorry about this... this is my first time running Server 2003.

Thanks,
LargeNostril

Can we assume you have added static entries in the tcp/ip
properties of the problem server? If so make sure default
gateway along with the subnet mask is correct. Also make
sure you have defined the DNS server as well. It may be
better for you to disable the DHCP service on the router
and have the W2k3 server hand out tcp/ip addresses along
with the correct gateway.
"LargeNostril" <(E-Mail Removed)> wrote:
> What would I need to check regarding routing? I have already tested
> various
> cat5/e cables and have tried several other NICs/computers on the router
> port
> my Server 2003 machine is connection to and I get the same results. What
> kind of settings should I be looking for in my router?
>
> Also, could this issue have anything due with my installation being the
> evaluation version?
>
> Sorry about this... this is my first time running Server 2003.
>
> Thanks,
> LargeNostril