Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
--- Steve Bertrand <[EMAIL PROTECTED]> wrote: > L Goodwin wrote: > > This is what I was hoping for. Thanks all! > > Well, even though this is a FreeBSD list and not a > Microsoft list, was > the problem resolved? What fixed it? > > > BTW, I did my second successful FreeBSD > installation > > this week on a server that I could not get it to > run > > on for the longest time. :-) > > Great! Now Google for Samba, and start posting your > pre-and-post FreeBSD > installation questions here ;) Actually, both of the FreeBSD servers I've set up so far are Samba servers. Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
At 07:40 PM 8/29/2007, L Goodwin wrote: I apologize for asking this question, but people who know UNIX often know a lot about operating systems in general. I have a client with a Windows 2000 Pro SP4 host. He cycled power without shutting down Windows, and now the Windows network (Network Neighborhood) is hosed. When he tries to access Network Neighborhood (from Windows Explorer), he get "Workgroup not available. The network name cannot be found.". This host can ping other hosts on LAN and has Internet access, and other hosts on LAN see this host and can access its shared resources (filesytem and printer), AND connect to it via VPN (it is set up as a VPN Host). What is the "correct" procedure for recovering from this mishap? TIA! :-) You need to unjoin the domain or workgroup, reboot. Then rejoin the domain or workgroup and reboot yet again. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
L Goodwin wrote: > This is what I was hoping for. Thanks all! Well, even though this is a FreeBSD list and not a Microsoft list, was the problem resolved? What fixed it? > BTW, I did my second successful FreeBSD installation > this week on a server that I could not get it to run > on for the longest time. :-) Great! Now Google for Samba, and start posting your pre-and-post FreeBSD installation questions here ;) Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
This is what I was hoping for. Thanks all! BTW, I did my second successful FreeBSD installation this week on a server that I could not get it to run on for the longest time. :-) --- Garrett Cooper <[EMAIL PROTECTED]> wrote: > Steve Bertrand wrote: > >> What is the "correct" procedure for recovering > from > >> this mishap? TIA! :-) > >> > > > > - download FreeBSD disk-1 from freebsd.org > > - insert CD into drive, and install :) > > > > Seriously.. > > > > It's been a while since I've actually managed a > Windows network per-se, > > but from what I recall, you can change the > workgroup to something else > > (then reboot), then re-assign the PC to the proper > workgroup (then > > reboot again), it may fix it. AFAIR, you can do > this by right-clicking > > on My Computer, and changing the computers > identity or name. > > > > If that doesn't work, then ensure that Norton or > some other so called > > 'firewall' or 'security suite' isn't blocking > outbound traffic via the > > NetBIOS protocol ports: > > > > # grep -i netbios /etc/services > > > > netbios-ns 137/tcp#NETBIOS Name Service > > netbios-ns 137/udp#NETBIOS Name Service > > netbios-dgm 138/tcp#NETBIOS Datagram > Service > > netbios-dgm 138/udp#NETBIOS Datagram > Service > > netbios-ssn 139/tcp#NETBIOS Session > Service > > netbios-ssn 139/udp#NETBIOS Session > Service > > > > Also, port 445 TCP and UDP may come into play > here. > > > > Interesting though that inbound is allowed/working > but outbound is fudged. > > > > Is this PC on a win2k Domain? Is there anything in > the 'logs' (stated > > very loosely) in the Event Viewer on the > remote/local hosts? > > > > Steve > > He hosed something with the network > configuration. > > *digs out old Windows tech support knowledge* > > 1. Executing: 'netsh int ip reset log' from > Start->Run will clean reset > the TCP/IP stack (it helps, on occasion). > 2. Uninstalling / reinstalling 'Client for Microsoft > Networks' and 'File > and Printer Sharing for Microsoft Networks' may be a > good bet if > something's corrupted. > 3. Adjusting 3rd party firewall rules to not block > ports 137-139 and 445 > (both TCP/UDP connection types) should eliminate the > problem, if any do > exist. > > And when all else fails.. backup and reinstall > (typically this is > less time consuming than root-cause debugging the > problem). With an OS > that age, your client really should be using XP > anyhow if he/she can > help it, because of the fact that it's not supported > by M$ anymore. > > Cheers, > -Garrett > Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
'kay. Thanks, J. --- Jonathan Horne <[EMAIL PROTECTED]> wrote: > On Wednesday 29 August 2007 19:40:09 L Goodwin > wrote: > > I apologize for asking this question, but people > who > > know UNIX often know a lot about operating systems > in > > general. > > > > I have a client with a Windows 2000 Pro SP4 host. > He > > cycled power without shutting down Windows, and > now > > the Windows network (Network Neighborhood) is > hosed. > > When he tries to access Network Neighborhood (from > > Windows Explorer), he get "Workgroup not > available. > > The network name cannot be found.". > > > > This host can ping other hosts on LAN and has > Internet > > access, and other hosts on LAN see this host and > can > > access its shared resources (filesytem and > printer), > > AND connect to it via VPN (it is set up as a VPN > > Host). > > > > What is the "correct" procedure for recovering > from > > this mishap? TIA! :-) > > > > youll probably want to start here: > > http://groups.google.com/groups/dir?&sel=33607436&expand=1 > > ... and now that thats out of the way... let the > flames begin! > -- > Jonathan Horne > http://dfwlpiki.dfwlp.org > [EMAIL PROTECTED] > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
Steve Bertrand wrote: What is the "correct" procedure for recovering from this mishap? TIA! :-) - download FreeBSD disk-1 from freebsd.org - insert CD into drive, and install :) Seriously.. It's been a while since I've actually managed a Windows network per-se, but from what I recall, you can change the workgroup to something else (then reboot), then re-assign the PC to the proper workgroup (then reboot again), it may fix it. AFAIR, you can do this by right-clicking on My Computer, and changing the computers identity or name. If that doesn't work, then ensure that Norton or some other so called 'firewall' or 'security suite' isn't blocking outbound traffic via the NetBIOS protocol ports: # grep -i netbios /etc/services netbios-ns 137/tcp#NETBIOS Name Service netbios-ns 137/udp#NETBIOS Name Service netbios-dgm 138/tcp#NETBIOS Datagram Service netbios-dgm 138/udp#NETBIOS Datagram Service netbios-ssn 139/tcp#NETBIOS Session Service netbios-ssn 139/udp#NETBIOS Session Service Also, port 445 TCP and UDP may come into play here. Interesting though that inbound is allowed/working but outbound is fudged. Is this PC on a win2k Domain? Is there anything in the 'logs' (stated very loosely) in the Event Viewer on the remote/local hosts? Steve He hosed something with the network configuration. *digs out old Windows tech support knowledge* 1. Executing: 'netsh int ip reset log' from Start->Run will clean reset the TCP/IP stack (it helps, on occasion). 2. Uninstalling / reinstalling 'Client for Microsoft Networks' and 'File and Printer Sharing for Microsoft Networks' may be a good bet if something's corrupted. 3. Adjusting 3rd party firewall rules to not block ports 137-139 and 445 (both TCP/UDP connection types) should eliminate the problem, if any do exist. And when all else fails.. backup and reinstall (typically this is less time consuming than root-cause debugging the problem). With an OS that age, your client really should be using XP anyhow if he/she can help it, because of the fact that it's not supported by M$ anymore. Cheers, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
> What is the "correct" procedure for recovering from > this mishap? TIA! :-) - download FreeBSD disk-1 from freebsd.org - insert CD into drive, and install :) Seriously.. It's been a while since I've actually managed a Windows network per-se, but from what I recall, you can change the workgroup to something else (then reboot), then re-assign the PC to the proper workgroup (then reboot again), it may fix it. AFAIR, you can do this by right-clicking on My Computer, and changing the computers identity or name. If that doesn't work, then ensure that Norton or some other so called 'firewall' or 'security suite' isn't blocking outbound traffic via the NetBIOS protocol ports: # grep -i netbios /etc/services netbios-ns 137/tcp#NETBIOS Name Service netbios-ns 137/udp#NETBIOS Name Service netbios-dgm 138/tcp#NETBIOS Datagram Service netbios-dgm 138/udp#NETBIOS Datagram Service netbios-ssn 139/tcp#NETBIOS Session Service netbios-ssn 139/udp#NETBIOS Session Service Also, port 445 TCP and UDP may come into play here. Interesting though that inbound is allowed/working but outbound is fudged. Is this PC on a win2k Domain? Is there anything in the 'logs' (stated very loosely) in the Event Viewer on the remote/local hosts? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
On Wednesday 29 August 2007 19:40:09 L Goodwin wrote: > I apologize for asking this question, but people who > know UNIX often know a lot about operating systems in > general. > > I have a client with a Windows 2000 Pro SP4 host. He > cycled power without shutting down Windows, and now > the Windows network (Network Neighborhood) is hosed. > When he tries to access Network Neighborhood (from > Windows Explorer), he get "Workgroup not available. > The network name cannot be found.". > > This host can ping other hosts on LAN and has Internet > access, and other hosts on LAN see this host and can > access its shared resources (filesytem and printer), > AND connect to it via VPN (it is set up as a VPN > Host). > > What is the "correct" procedure for recovering from > this mishap? TIA! :-) > youll probably want to start here: http://groups.google.com/groups/dir?&sel=33607436&expand=1 ... and now that thats out of the way... let the flames begin! -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4
I apologize for asking this question, but people who know UNIX often know a lot about operating systems in general. I have a client with a Windows 2000 Pro SP4 host. He cycled power without shutting down Windows, and now the Windows network (Network Neighborhood) is hosed. When he tries to access Network Neighborhood (from Windows Explorer), he get "Workgroup not available. The network name cannot be found.". This host can ping other hosts on LAN and has Internet access, and other hosts on LAN see this host and can access its shared resources (filesytem and printer), AND connect to it via VPN (it is set up as a VPN Host). What is the "correct" procedure for recovering from this mishap? TIA! :-) Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
