|
Home > Archive > microsoft.public.sqlserver.server > June 2002 > New Network Card Now Can't Connect in EM by Name
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
New Network Card Now Can't Connect in EM by Name
|
|
| Peter Fournier 2002-06-24, 1:12 pm |
| Sounds like a routing problem if both cards are active.
Check out your netstat -R and see what your routing table
looks like. May want to talk w/your network folks and get
them in to resolve it. Usually just a matter of adding
some routes.
Peter Fournier
peterfournier@fournierw
are.com
www.fournierware.com
>-----Original Message-----
>The server administrator installed a second network card
in my sql 2k sp2,
>W2k Advanced server yesterday. This morning I discovered
that I cannot
>connect to it in EM by servername. I can only connect to
it by using the
>original ip address. I cannot connect to it by using the
new ip address
>(which will eventually only be used for specific traffic -
not sql). If I
>ping the server by name it resolves to the new ip
address. I don't see any
>other problems with this except in EM.
>
>The new NIC card is set to 10 Mbps (no more 100 Mbps
ports are available on
>the switch). The tcp/ip properties of the new NIC include
a WINS server
>(which is not really needed).
>
>1. Should I look for other problems?
>
>2. What could be causing this?
>
>3. Would adding a WINS server for the original NIC help?
>
>Also, sorry about the cross-post to sqlserver.connect but
this is one of the
>many newsgroups that I check regularly that for some
reason has no new posts
>since 6/13 (including mine).
>
>Michelle
>
>
>
>
>.
>
| |
| Michelle 2002-06-28, 9:25 am |
| The server administrator installed a second network card in my sql 2k sp2,
W2k Advanced server yesterday. This morning I discovered that I cannot
connect to it in EM by servername. I can only connect to it by using the
original ip address. I cannot connect to it by using the new ip address
(which will eventually only be used for specific traffic - not sql). If I
ping the server by name it resolves to the new ip address. I don't see any
other problems with this except in EM.
The new NIC card is set to 10 Mbps (no more 100 Mbps ports are available on
the switch). The tcp/ip properties of the new NIC include a WINS server
(which is not really needed).
1. Should I look for other problems?
2. What could be causing this?
3. Would adding a WINS server for the original NIC help?
Michelle
| |
| James Luetkehoelter 2002-06-28, 10:25 am |
| Well, if you can ping it with the old address, but pinging
by name gives you the new nic's address, name resolution
is obviously now registered to the new nic via WINS or
DNS. If you ping it by name, it necessarily has to return
only a single IP address.
What you'll need to do is to create an entry in your local
hosts of lmhosts file for that server specifying the
original IP address. Otherwise, you'll have to just use
the IP address. You could also make a client side alias
with the Client Network utility to assign a name to use
instead of the IP address.
Another option would be to add an additional WINS or DNS
entry for the original NIC. So you'd have to entries for
that server: SERVER1 resolves to the original IP, SERVER2
resolves to the new IP. It all really depends on how your
network admin wants to handle it. Local hosts/lmhosts
files can be an administrative nightmare, so I'd guess
that adding a second WINS/DNS entry would be best.
Hope that helps a little.
>-----Original Message-----
>The server administrator installed a second network card
in my sql 2k sp2,
>W2k Advanced server yesterday. This morning I discovered
that I cannot
>connect to it in EM by servername. I can only connect to
it by using the
>original ip address. I cannot connect to it by using the
new ip address
>(which will eventually only be used for specific traffic -
not sql). If I
>ping the server by name it resolves to the new ip
address. I don't see any
>other problems with this except in EM.
>
>The new NIC card is set to 10 Mbps (no more 100 Mbps
ports are available on
>the switch). The tcp/ip properties of the new NIC include
a WINS server
>(which is not really needed).
>
>1. Should I look for other problems?
>
>2. What could be causing this?
>
>3. Would adding a WINS server for the original NIC help?
>
>
>Michelle
>
>
>
>
>
>
>.
>
|
|
|
|
|