Discussion Locked

IP Address??

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
All machines are Win 98/95 and the server is NT 4.0 w/SP6. Using TapeWare 6.20 SP3D for backup purposes. Problem machines are 1 & 2. The entire network including problem machines can see and access 1 & 2 just fine. here's the problem, 1 & 2 can't bebacked up by TapeWare because TapeWare uses the wrong IP Address "0.0.0.1", to communicate with 1 & 2. Also, when pinging 1 or 2 from itself, "0.0.0.1" is what is pinged. Not the correct IP Address for the machine. Have tried everything I can think of including working with TapeWare to resolve. We narrowed it down to the machine itself. It is not TapeWare. I've been working on this for weeks. Help!!!!

14 replies

by paul d. masley

Check your MAC addresses on all three network cards (server and 1 & 2). You may have been one of the lucky few to get cards with the same addresses.

by dswartz

I didn't have this problem until I reformatted 1 & 2 and they worked fine before. Thanks for your suggestion.
DES. . .

by Member 21361443

I'm not familiar with TapeWare, but here are a couple of thoughts.

Do you have a HOSTS file? If you do, might you have the wrong addresses in it?

Can you ping 127.0.0.1 from those machines with success?

Have you removed TCP/IP and reinstalled it, including the latest patches from MS?

Are you using DHCP or hand-keyed IPs? If hand-keyed, do you have multiple NICs or extra modems in those machines? You may need to remove any extra NICs or modems.

If you are using DHCP, will it let you release and renew your IP address?

Sorry, best I can do is hopefully point out some standard networking issues.

Good luck!
Brian Lusk

by dswartz

The network sees 1 & 2 as IP Address "10.1.2.7" for 1 and "10.1.2.15" for 2. But they both see themselves as IP Address "0.0.0.1". If I'm on machine 1 and select Start, Run, Command and type "ping 1" and hit enter, it pings IP Address "0.0.0.1", not"10.1.2.7". 1 only represents a machine name. It is not the actual machine name. Please give me more ideas.
DES. . .

by tuck46

go to machine 1, start, run, type in winipcfg, release the IP and power off the machine. Then go to machine 2, start, run, type in winipcfg, release ip then renew. Go back to machine 1, start windows,strt, run, winipcfg and click renew. this should assign a unique IP.

by dswartz

All IP's are hand keyed for each machine. Thank you for the suggestion.
DES. . .

by rmiller

The problem is the name of the computer. Don't use 1, 2, etc as the computer name must have a non-numeric character in it. It interperets the 1 as a shortcut for putting in the I.P address.

by michael roark - ccna/da mcp 3csa

OK, so you're not using DHCP, do you have a WINS server? and a LMHOSTS file? there is obviously something telling your computer name to resolve as 0.0.0.1; Do you know which protocol Tapeware uses? that would be the first step, whether it's a Winsock program, or etc. ; What kind of stack do you have on the computers that are working and the two that can't be backed up?? (the protocol stack). have you tried shutting down one of the computers that can be backed up, assigning #1 or #2 that one's IP and then attempting to backup. That may give you a clue if it's in your TCP/IP stack, or narrow it down to NBT (NetBios over TCP/IP)

by james_randy

Since you rejected all those answers, why don't you just close your question?

If you are still tackling this problem, perhaps you should consider calling your local super-hero.

This discussion is closed to new replies.