2 IP Address's & Mapping Problem

Having a mapping problem with the "second IP address" of the SINGLE NIC...........

Windows NT 4.0 Server allows you to have more than 1 IP address per NIC.

What I've done:
The original IP to the server was on the "167 network ". Using the ADVANCED IP Addressing, I added a second address on the "192 network "

Testing:
I am now able to ping servers on both networks. That's fine in both directions.

Problem:
I cannot map a drive from this server to anything on the "192 network ". Nothing on the 192 network even appears in Network Neighborhood. I tried mapping from another server on 192 TO THIS machine, and that does not work either. I can map to machines on the 167 network with no problem

I dabbled with a few different LMHOST and GATEWAY tricks, but NG.

IS THIS AN NT THING?

WHAT DID I MISS?

IS IT BECAUSE ONLY 1 OF THE IP's CAN BE THE "PRIMARY IP ADDRESS "?

Thanks in advance

 

Since you can ping by IP address it sounds as if your connecting to the IP network ok. The problem seems to be a name resolution problem most likely attributed to WINS. Do you have a WINS server in your "192" network? If so, do you have that additional WINS server IP address added to your TCP/IP config?

 

It appears that NetBIOS will only bind to the primary IP address so Network Neighborhood, mapping drives, etc. probably won't work on the secondary IP address alone.

 

There is no WINS server running on either network. Actually, the 167 network is a domain, and the 192 network is a workgroup (2 servers, 3 workstations). With regard to the WINS server, I was under the impression that a WINS server is used to cut down on broadcast traffic when "calls" are made via NETBIOS names. In this situation, I tried to do the mapping via IP address. Then thinking it may have been a NETBIOS thing, I added the LMHOST file referring the machine name on the 192 network to it's IP address. This LMHOST file was added to the 167 machine that I was attempting to do the mapping with.

Looks like it's time to add the 'ole second NIC card to the 167 machine

 

If the 192 network is only a workgroup it could be simply rights (as connectivity looks OK by PING)

exactly what error message do you get when you try and connect to the name ?

can you map drive to \\192.x.x.x\share name ?