Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Invalid Network Address 1

Status
Not open for further replies.

PS40

Vendor
May 29, 2003
8
US
We have a customer who has a mixed 2000, NT and Netware environment. The main server we will call T1 is a DC setup with DNS, DHCP, WINS. All clients are mixed 95 and 2000 can connect to T1 and the other 2000 member servers. The 2000 member servers can connect to T1. The DC, T1, can see the other servers in network places. When you try to open up the server you get an error 'network address is invalid'. You can however open up the NT server and Novell server with no problems. If you try using 'Net Use' from T1 you get the same error. Only going into explorer will allow you to map a drive. The problem was noticed, not being able to open this up in network places is that for installing Symantec AV to other servers and adding resources to Veritas backup it needs to connect to the Admin$ on the other servers. Doing a map to Admin$ works but you still get invalid network address in explorer, NAV or Veritas. There was one article on Vertitas that said if you are using the Novell client, which T1 is, to set the provider order to Microsoft first, Netware second. Made that change and still have the same problem and error. Any direction would be appreciated.
 
"...to set the provider order to Microsoft first, Netware second" You mean that you set the binding order to TCP/IP 1st and NWLINK 2nd in both File and Print and client for MS Networks?

Hewissa

MCSE, CCNA, CIW
 
No, according to Veritas they wanted you to go to Right Click Network Places, Properties, Advanced, Advanced Settings, click on Provider Order Tab and change order there to have Microsoft Windows Network as first provider.
 
Change the binding order also then. Move TCP/IP above NWLink in all casses. Same location, just one step further.

Hewissa

MCSE, CCNA, CIW
 
Changing the binding order and restarting the server solved this problem. Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top