Re: NETBIOS problem
From: David Copeland [MSFT] (davidcop_at_online.microsoft.com)
Date: 09/24/04
- Next message: SuperGumby [SBS MVP]: "Re: It was so SIMPLE!"
- Previous message: Jay: "Re: Connect to SQL via internet"
- In reply to: Cris Hanna [SBS-MVP]: "Re: NETBIOS problem"
- Next in thread: Shane Jimerfield: "Re: NETBIOS problem"
- Reply: Shane Jimerfield: "Re: NETBIOS problem"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 24 Sep 2004 16:21:28 -0500
Shane,
Where is the machine pointing to for WINS/DNS.. if you are able to ping by
IP address, and net view by IP address... then it sounds like you just need
a way to resolve the host/netbios names to the proper IP address. Also,
keep in mind that if at least one machine on the remote subnet is not a
member of the domain then network neighborhood browsing may not work..
(needs a subnet master browser for the domain master browser (PDC) to
replicate with)
Also, keep in mind that just because you don't see a machine in network
neighborhood doesn't mean that you can't connect to it... and just because
you can see a machine doesn't mean you will be able to connect to it.. due
to timings of machines broadcasting and the browse list being replicated to
the domain master browser and back to subnet master browsers (can take up to
~1hr depending on network configurations)
Can you ping the fqdn name of the server from the remote client? include the
trailing period. For example..
ping primus.yourdomainname.local.
Make sure that the wired/wireless nics are on different subnets..
-- Hope that helps, David Copeland Microsoft Small Business Server Support This posting is provided "AS IS" with no warranties, and confers no rights. SBS Newsgroups: SBS v4.x: microsoft.public.backoffice.smallbiz SBS 2000: microsoft.public.backoffice.smallbiz2000 SBS 2003: microsoft.public.windows.server.sbs "Cris Hanna [SBS-MVP]" <crishannanospam@computingnospampossibilities.net> wrote in message news:eGYXOpnoEHA.3464@tk2msftngp13.phx.gbl... Only thing I haven't seen you do is replace the nic. If you have a wired and wireless nic in the machine...typically only one really "connects" try disabling one of them "Shane Jimerfield" <remove.sj@biologicaldiversity.org> wrote in message news:eLTl6anoEHA.800@TK2MSFTNGP14.phx.gbl... Sorry to post this here, but I've not been able to get help on the XP lists. And I've gotten good help here before so...please don't hate me. Here's the problem. I have remote office with a peer-peer windows workgroup. All computers can see the workgroup fine, except one (let's call it computer A). The only way that computer A can see the workgroup is when I disconnect computer B's NIC from the LAN. Here are the many steps that I've taken on computer A: 1) When I click "Show workgroup computers" i get "CBDNET is not accessible. You may not have permission to use this network resource. The list of servers for this workgroup is not currently available." 2) When I run "Net View" from the command prompt i get "System error 6118 has occurred. The list of servers for this workgroup is not currently available" 3) If i run "Net View \\primus" I get "System error 53 has occurred. The network path was not found." 4) If i run "Net view \\192.168.4.242" (which is the IP for primus then it works) then it shows me the resources. 5) If I ping Primus i get "Ping request could not find host primus. Please check the name and try again." 6) If i ping 192.168.4.242 then it works. Here are few things I've done: 1) I've made sure that NETBIOS over TCP/IP is enabled. 2) I've added the following exceptions in Widows Firewall TCP and UDP for ports 136-139 both incoming and outgoing. 3) I've renamed the computer. 4) I've checked to see that all machines are on the same workgroup, "CBDNET" 5) I've tried disableling the firewall. 6) I've checked to see that the "COmputer Browser" service is running. 7) I've flushed DNS 8) I've run "netsh int ip reset reset.txt" 9) I've run "netsh winsock reset catalog" 10) I've made sure that file and print sharing is enables 11) I've ensured there are no other protocal running other than TCP/IP, like IPX. The only thing that I'm not sure about are duplicates of NETBIOS names. If a computer has two connections one wired and wireless can that cause NETBIOS problems? Any help would be great! Shane
- Next message: SuperGumby [SBS MVP]: "Re: It was so SIMPLE!"
- Previous message: Jay: "Re: Connect to SQL via internet"
- In reply to: Cris Hanna [SBS-MVP]: "Re: NETBIOS problem"
- Next in thread: Shane Jimerfield: "Re: NETBIOS problem"
- Reply: Shane Jimerfield: "Re: NETBIOS problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|