Hello



I'm trying to map network shares using my logon scripts (KIX, AD, Win

20003).

When I use  \\_server_name\share_name - it works fine.

When I use  \\_DFS_name\share_name - it hangs on executing login script.

;((



DFS - Distributed File SyStem



Does login script not support DFS names ???



TIA

Roman

In news:e6DSOPRVEHA.1380@TK2MSFTNGP09.phx.gbl,

Roman <o211@o2.pl> posted their thoughts, then I offered mine

> Hello

>

> I'm trying to map network shares using my logon scripts (KIX, AD, Win

> 20003).

> When I use  \\_server_name\share_name - it works fine.

> When I use  \\_DFS_name\share_name - it hangs on executing login

> script. ;((

>

> DFS - Distributed File SyStem

>

> Does login script not support DFS names ???

>

> TIA

> Roman



Sure it supports it. It would be mapped by:

\\domain.com\sharename



If you're having DNS issues, that will definitely cause a problem.



--

Regards,

Ace



Please direct all replies to the newsgroup so all can benefit.

This posting is provided "AS-IS" with no warranties and confers no

rights.



Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP

Microsoft Windows MVP - Active Directory



HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a

pig. --

=================================

I am also experiencing this problem. 

I have noticed that I can "Run" the DFS path, but cannot Map to it (Dialog box or net use.)

Once run, it will map. 

Note: DNS is working fine.




	
Quote:
	

	

		

			
				Originally posted by Roman 

Hello



I'm trying to map network shares using my logon scripts (KIX, AD, Win

20003).

When I use  \\_server_name\share_name - it works fine.

When I use  \\_DFS_name\share_name - it hangs on executing login script.

;((



DFS - Distributed File SyStem



Does login script not support DFS names ???



TIA

Roman 
			
		
	
	

In news:eamse.18n3v3@mail.mcse.ms,

eamse in <eamse.18n3v3@mail.mcse.ms> posted their thoughts, then I offered

mine

> I am also experiencing this problem.

> I have noticed that I can "Run" the DFS path, but cannot Map to it

> (Dialog box or net use.)

> Once run, it will map.

> Note: DNS is working fine.

>



Do you have any event log errors?





--

Regards,

Ace



Please direct all replies ONLY to the Microsoft public newsgroup so all

can benefit. This posting is provided "AS-IS" with no warranties and

confers no rights.



Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP

Microsoft Windows MVP - Active Directory



HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a

pig. --

=================================

Ok, here goes, my experiences to date.....



no errors, no logs, it just doesn't work. BUT...



We first noticed the problem after patching our servers with some hot fixes from Micorsoft. 

811630

810649

814033

329553

(You can't remove some of these, bugger)



I have logged a case with Microsoft who have examined all our servers and come up with the solution to remove the DFS root on one of the servers. Problem is this issue affects all servers.

One thing that bugged me was that the mapping to the users 'F' drive (DFS path) failed, not every time, but often enough to be a complete pain. But the mapping the DFS root worked every time ('U' Drive) and the users with multiple DFS drive mappings only lost 'F' drive.



I played with the logon script and found that the first DFS mapping fails.  Regardless of where it points in the DFS structure. The subsequent ones all work.



Thats where I'm up to.



We're currently usig UNC paths for mapping, but to get back to DFS I may try a useless mapping of a 'B' drive to a DFS path and hope it fails, allowing the users to get all the normal drives.

In news:eamse.18ounz@mail.mcse.ms,

eamse in <eamse.18ounz@mail.mcse.ms> posted their thoughts, then I offered

mine

> Ok, here goes, my experiences to date.....

>

> no errors, no logs, it just doesn't work. BUT...

>

> We first noticed the problem after patching our servers with some hot

> fixes from Micorsoft.

> 811630

> 810649

> 814033

> 329553

> (You can't remove some of these, bugger)

>

> I have logged a case with Microsoft who have examined all our servers

> and come up with the solution to remove the DFS root on one of the

> servers. Problem is this issue affects all servers.

> One thing that bugged me was that the mapping to the users 'F' drive

> (DFS path) failed, not every time, but often enough to be a complete

> pain. But the mapping the DFS root worked every time ('U' Drive) and

> the users with multiple DFS drive mappings only lost 'F' drive.

>

> I played with the logon script and found that the first DFS mapping

> fails.  Regardless of where it points in the DFS structure. The

> subsequent ones all work.

>

> Thats where I'm up to.

>

> We're currently usig UNC paths for mapping, but to get back to DFS I

> may try a useless mapping of a 'B' drive to a DFS path and hope it

> fails, allowing the users to get all the normal drives.



Interesting that the script is doing that. Curious why the first mapping

won't work. But an interesting to use a 'dummy' intial mapping. :-)



I'm assuming that you are only using your internal DNS and not an ISPs? I

usually ask that just to eliminate that source of error.



Curious what PSS comes up with on this.





--

Regards,

Ace



Please direct all replies ONLY to the Microsoft public newsgroup so all

can benefit. This posting is provided "AS-IS" with no warranties and

confers no rights.



Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP

Microsoft Windows MVP - Active Directory



HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a

pig. --

=================================

Yep, we're using our own internal DNS.

No errors there, FRS is also happy.



Even tried \\FQND\DFSroot



I've also tried a 20 sec delay to eliminate any timing issues, but still the first mapping fails.

	
Quote:
	

	

		

			
				Originally posted by eamse 

Yep, we're using our own internal DNS.

No errors there, FRS is also happy.



Even tried \\FQND\DFSroot



I've also tried a 20 sec delay to eliminate any timing issues, but still the first mapping fails. 
			
		
	
	
Forgot this point. 



Using a packet sniffer I can see the request for the DFS mapping goto the server and the server (Hosts a copy of the DFS root, has the actual share and folders.) rejects the request with a STATUS_OBJECT_PATH_NOT_FOUND.

4 packets later it happily accepts the next request.

In news:eamse.18pjnz@mail.mcse.ms,

eamse in <eamse.18pjnz@mail.mcse.ms> posted their thoughts, then I offered

mine

> eamse wrote: 

>

> Forgot this point.

>

> Using a packet sniffer I can see the request for the DFS mapping goto

> the server and the server (Hosts a copy of the DFS root, has the

> actual share and folders.) rejects the request with a

> STATUS_OBJECT_PATH_NOT_FOUND.

> 4 packets later it happily accepts the next request.



Hmm. Interesting finding. Let me know what PSS has to say about this please!



--

Regards,

Ace



Please direct all replies ONLY to the Microsoft public newsgroup so all

can benefit. This posting is provided "AS-IS" with no warranties and

confers no rights.



Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP

Microsoft Windows MVP - Active Directory



HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a

pig. --

=================================