Accessing thro NETBIOS

Similar Threads:

1.Problem accessing RAS thro VPN!!

Hello all,

Here's the configuration.
We have a windows2003 small business server installed on a HP server as a 
domain controller. This server has been configured as a Remote Access Server 
to allow users to connect to the server thro the internet. A router has been 
installed for external connectivity. what we noticed is, if we configure NAT 
in the Router VPN doesn't work, that means users are not able to connect to 
the server thro VPN or VPN dialer.  If the router is configured as a bridge, 
VPN works fine, we can login thro terminal services and take control of the 
server without any problems. But, this disables internet connectivity for the 
desktop pc's in the intranet. Is it possible to have both NAT working in the 
router and internet working for the pc's in the intranet? And, the server has 
only one network card, do i have to install a second one to accomplish this? 
can't we do it one nic.

Any help is appreciated.
Skirao

2.Accessing Applications thro Terminal Services

I have a win 2k3 server- when i try accessing a particular application (an 
accounting software) through remote connection, it shows an error message 
saying a particular dll file is not available. This problem does not occur 
when i log on as 'administrator' but any other user with administrative 
rights faces this problem! Can anyone help?!

3.Disabling NetBIOS and NetBIOS style domain name

Hello,

Can somebody explain me how AD where client and servers 
are having NetBIOS disabled able to logon clients using 
NetBIOS domain name?
For example I have domain called test.com with NetBIOS 
name TEST. So when I logon to workstation I don't specify 
UPN (@test.com) but rather leave DOMAIN field populated 
with TEST domain.
Question is how AD client resolves this TEST name using 
DNS?

G

4.Cant ping fqn or netbios, but can map netbios but not fqn

I have a weird issue going on.  I have a windows 2003 host that is
part of a domain.  It has two nics in the box:

10.201.8.31 - LAN ADAPTER
255.255.255.0 - Subnet Mask
10.201.8.1 - Gatway

10.201.8.32 - NLB ADAPTER
255.255.255.0 - Subnet Mask
no gatway defined

For some strange reason I cant ping the box called lets say:

duane-haas.com - 10.201.8.2

Cant ping by name, cant by direct to the ip, but I can ping other
hosts on the network 10.201.8.x just fine.  I can actually map a drive
to a share on duane-haas via the command line using the netbios name,
and it connects, but when you try to map using the fqn it doesnt
connect.  Also, if I disable the NLB adapter everything works, when I
enable the NLB adapter things work as described above.  Its really
starting to drive me nuts?????  I have another box on the same network
that is configured the same way, and although the host was having the
same problem on wednesday, it seemed to go away after rebooting the
box wednesday night, also rebooted this box wednesday night but it
continues to have the problem.

5.Need TCP NetBIOS Helper to Access Active Directory Server

On Windows 2000 machines on our network, if you look up the Active Directory
name with:

    nslookup corp.mydomain.com

this resolves to the IP address of the Active Directory server.    If
however you simply try to access it directly with:

    dir \\corp.mydomain.com\sysvol

this fails with a message that the location cannot be resolved.

As soon as you turn on the TCP/IP NetBIOS Helper service, now you are able
to access the AD server using its fully-qualified DNS name.   Why in the
world would you need a NetBIOS Helper service to locate an AD server using
its direct DNS name?    At very least that creates a security problem
doesn't it?   Even with NTLM disabled, does the file service still use some
form of NETBEUI protocol?   What specific components within TCP/IP NetBIOS
Helper service do we need here?

-- 
Will

6. Sudden loss of remote Netbios access over TCP/IP

7. Netbios & Routing and remote access

8. netbios access problem