Re: \\domainname.com\SYSVOL\ is not browseable
From: David Lewis (user_at_microsoft.com)
Date: 01/20/05
- Previous message: Glyn Williams: "dynamically update DNS server"
- In reply to: Kevin D. Goodknecht Sr. [MVP]: "Re: \\domainname.com\SYSVOL\ is not browseable"
- Next in thread: David Lewis: "Re: \\domainname.com\SYSVOL\ is not browseable"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 20 Jan 2005 12:46:25 -0800
any more thoughts on this issue from anyone else?
"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US>
|>In news:b6qou0tmms401ug21k1tkd11vai374rk15@4ax.com,
|>David Lewis <user@microsoft.com> commented
|>Then Kevin replied below:
|>> Still have this issue. This thread is almost a month
|>> now. Have had the problem for months
|>
|>Believe me, you are not the first to have this issue in XP and nobody wants
|>this resolved more than me. If I could reproduce the same behavior on my
|>son's XP Pro client it would help a lot.
|>
|>Let us try this, try connecting to the DFS share by the domain NetBIOS name
|>like this \\domainNetbiosName\sysvol
|>
|>Whether it works or not send me the results from this command:
|>net start
|>This command will list the running services, I'd like to compare it to my XP
|>Pro client. May be there is something in it that should be running
- Previous message: Glyn Williams: "dynamically update DNS server"
- In reply to: Kevin D. Goodknecht Sr. [MVP]: "Re: \\domainname.com\SYSVOL\ is not browseable"
- Next in thread: David Lewis: "Re: \\domainname.com\SYSVOL\ is not browseable"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|