wizzywig1970
asked on
NetBIOS over TCP/IP enabled
I have created a dial-up connection to my company. Once I have successfully dialed in, I go to Pcanywhere to connect to my pc. I am able to connect to my pc via my IP address from PCanywhere, but I cannot use my pc name. I try to ping my pc name but I get an error. I can ping my ip address of the computer. When I do an ipconfig a I see that NetBios over TCP/IP is disabled.
I think this may be the problem.
How do I enabled it? I right-click the dial-up connection, go to networking, click on TCP/IP, properties, advanced, WINS, but I do not see the "NetBios setting" options so I can enable NetBios over TCP/IP.
Any suggestions?
Thanks,
George
I think this may be the problem.
How do I enabled it? I right-click the dial-up connection, go to networking, click on TCP/IP, properties, advanced, WINS, but I do not see the "NetBios setting" options so I can enable NetBios over TCP/IP.
Any suggestions?
Thanks,
George
What operating system are you using.
ASKER
Win 2000 Professional
Where do you want to see your name? Try this,
Ping -a ###.###.###.###
where the "###" gets you IP address of your machine. If you can ping it from another box and get a response in time, but it does not list a name, it is because the name to place there is supposed to be housed on a DNS server that can do the name/address association.
nbtstat -n
> Win 2000 Professional
I thought that for that OS and above, that MS made NetBios always run under TCP, such that we no longer choose the outdated NetBeui my mistake.
But for NetBios to use name for lookups such as through explorer you have to have the WINS servers running.
Ping -a ###.###.###.###
where the "###" gets you IP address of your machine. If you can ping it from another box and get a response in time, but it does not list a name, it is because the name to place there is supposed to be housed on a DNS server that can do the name/address association.
nbtstat -n
> Win 2000 Professional
I thought that for that OS and above, that MS made NetBios always run under TCP, such that we no longer choose the outdated NetBeui my mistake.
But for NetBios to use name for lookups such as through explorer you have to have the WINS servers running.
> I try to ping my pc name but I get an error.
Ping is NOT a MS term, this relates to name associations in TCP, namely the ones stored in the DNS server. The "ping -a " command option should reveal a name that is associated with the IP, whether it is accurate or not.
Talk to admin of the DNS server, and get yourself listed if you want to use the name. These names are usually only used for servers, not for workstations. Note that the name is not any of the names you personally call your client. It is only what the DNS server claims. You can make them same if you want to, most people do. Only problem is when seeing the name one still has no clue which protocol is refered to, or where the same name may be updated.
Ping is NOT a MS term, this relates to name associations in TCP, namely the ones stored in the DNS server. The "ping -a " command option should reveal a name that is associated with the IP, whether it is accurate or not.
Talk to admin of the DNS server, and get yourself listed if you want to use the name. These names are usually only used for servers, not for workstations. Note that the name is not any of the names you personally call your client. It is only what the DNS server claims. You can make them same if you want to, most people do. Only problem is when seeing the name one still has no clue which protocol is refered to, or where the same name may be updated.
The easiest thing for you to do would be to add an entry to your lmhosts file. Creating a DNS entry is somewhat overkill since you are seemingly the only person that wants to connect to the remote machine by name.
There is a sample host file called lmhosts.sam under
%systemroot%\system32\driv
in W2K.
Grab this file, open it in notepad and add an entry for the machine you want to connect to by name. This is very similiar to creating an A record on the DNS server, accept that you will be the only person able to access your machine by the name you assign in the host file. The file has some excellent instructions on creating an entry.
Once you've made your entry to the host file, rename the file to:
lmhosts
(remove the .sam extension) and leave it in the same directory.
There is a sample host file called lmhosts.sam under
%systemroot%\system32\driv
in W2K.
Grab this file, open it in notepad and add an entry for the machine you want to connect to by name. This is very similiar to creating an A record on the DNS server, accept that you will be the only person able to access your machine by the name you assign in the host file. The file has some excellent instructions on creating an entry.
Once you've made your entry to the host file, rename the file to:
lmhosts
(remove the .sam extension) and leave it in the same directory.
ASKER
The problem is this. I am setting up this laptop for a user to take home and dial into work. Right now when I set up the PC Anywhere connection, I have to set it up using the IP address of her PC. This works fine, but this will cause problems when she obtains a new IP address or maybe even gets a new pc. Because I setup her PC Anywhere to connect via IP address she will no longer be able to connect to her pc when and if the IP address . This is why I would like to set PC Anywhere connection to connect using her PC Name since that will not change. Here lies the problem, I cannot use the PC name, because I get back an error indicating the requested host cannot be found. I had previously been able to setup laptops to connect using PC Anywhere using the computer name,but this one is giving me problems?
A simple solution to this is to use a dynamic host name service. I use TZO (http://www.tzo.com). For a small fee, they will give you a hostname (myhost.tzo.com), and a small program that will watch for your IP to change.
Whenever your IP address changes, TZO will update their records to reflect the change, so connecting to myhost.tzo.com (use whatever name you want, as long as it's available instead of myname) will always connect you to the correct IP address.
Greg
http://parallel.tzo.com
:)
Whenever your IP address changes, TZO will update their records to reflect the change, so connecting to myhost.tzo.com (use whatever name you want, as long as it's available instead of myname) will always connect you to the correct IP address.
Greg
http://parallel.tzo.com
:)
Are you using WINS?
Don't need to use WINS. It's a dynamic name service.
--Greg
--Greg
...WINS for his internal network. My speculation is that if he has to dial in to his corporate network before he initiates PCAnywhere, they are probably using NAT or PAT to connect outside. Otherwise, if the addresses were public, he could simply initiate the PCAnywhere connection without having to dial.
If he's dialing into his corporate network, he'll be on an address space that's routable to them inside. If WINS is enabled and passed to the RAS pool, then he wouldn't need to know what address the machine was, he could always access the machine by it's NetBios name since WINS would track the changes.
If he's dialing into his corporate network, he'll be on an address space that's routable to them inside. If WINS is enabled and passed to the RAS pool, then he wouldn't need to know what address the machine was, he could always access the machine by it's NetBios name since WINS would track the changes.
ASKER
Problem has been resolved. I right-clicked on my dial-up connection and went to properties. TCP/IP was the only thing selected. I then also selected Fiel and print sharing and client for Microsoft networks and then I was able to connect to any pc via PC Anywhere by using the Computer name, not the IP address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
> I then also selected Fiel and print sharing and client for Microsoft networks
Opening Sharing? -talk about vulnerabilities!
> and then I was able to connect to any pc
Not at all true. MS Networking, as said above, uses NetBios and Wins. NetBios is not routable. In newer MS it can tunnel in TCP, but that would be required of both ends of communication. And both would need access to same WINS server. I guarantee you that you will NOT be able to connect to my PC. This is very very very different from TCP, which will add every single address association to DNS. The difference is like the diff between LAN and WAN, or intranet vs internet. They look similar but requirements and functionality can be enormously different.
Opening Sharing? -talk about vulnerabilities!
> and then I was able to connect to any pc
Not at all true. MS Networking, as said above, uses NetBios and Wins. NetBios is not routable. In newer MS it can tunnel in TCP, but that would be required of both ends of communication. And both would need access to same WINS server. I guarantee you that you will NOT be able to connect to my PC. This is very very very different from TCP, which will add every single address association to DNS. The difference is like the diff between LAN and WAN, or intranet vs internet. They look similar but requirements and functionality can be enormously different.
Thanx. -Good Fortune-