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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

problem with terminal server IP address

Status
Not open for further replies.

Vic88

MIS
May 29, 2000
76
0
0
JM
I just installed a new Windows NT Terminal Server. Initially it had the IP assress 192.168.0.5. This was changed to the static address 192.168.1.1. whenever I ping the server netbios name, the initial address came up.


How can I correct this ?
 
Try to reboot. Maybe the problem is that WINS hasn't been updated yet (with the new ip address).

The Terminal Server must be using the new IP address right? When you do an IPCONFIG /all from a command prompt, you should see the correct IP address: 192.168.1.1

Make sure that you have the correct WINS addresses on the Terminal server.

Do you get a response from the server when you ping the IP address of the term server remotely?

Do you get a response from the server when you ping the Netbios name? (or does this time out?)

-later

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
You can force a WINS refresh with

nbtstat -RR

from the command prompt, if that helps?

Andy Leates MCSE CCNA MCP+I
 
If the server rebooted after the change it would have released its WINS entries. Its possible that it WAS entered into WINs as a Static entry though you would probably ne seeing some duplicate name error if so. You check for static entries in WINS Manager.

If not that, on the machine where you are getting the old one did you check the hosts and lmhosts files for entries for that machine?
 
and also check your lmhosts file for any references.

cheers,
hanz.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top