Cannot access Network Shared Drives over Corporate Network on Wireless

I cannot find a link to the paper that I was looking for - but it deals with the way users authenticate to Cisco APs, then the AP passes the authentication on to the AD. We had problems with this many years ago and we are still using Cisco's work around for the issue.

For what it is worth, we also have had lots of problems with DFS shares.
IT did the same work around. i.e. bypass the DFS server.

UsernameIssues said:

As I understand it...
...the OP had the letters M and S mapped using DFSROOT share target
\\domain.com\sharename

The IT staff went around the DFS server and supplied the OP with
\\servername\sharename
to be used as the target.

wow so it's a "comon" problem.

YESSS!!!!

so what i did now is the following:

since at every reboot S and M are recreated automatically, i opened the registry, found the Network shares and i edited the \\domain.com\sharename with \\servername\sharename and works PERFECT!!!

HKEY_CURRENT_USER\Network

I know is nasty but it works fine :)

Now i am stuck with my "homefolder" basically is another network drive, "H" that is created at every restart which i cannot find under the above key, and again, gives me trouble, it is not synchronized, but then again, if i use \\servername\HomeFolders\gabrio i can access it just fine.

actually if there's a way to prevent this to be recreated every time at restart, that would work.

I can create a new network mapping with \\servername\HomeFolders\gabrio but then at every restart there's two, one working and one not.

thanks guys and sorry if complicated to explain!

Gabrio

Kaktussoft said:

Look at this What is DFS (Distributed File System)
Especially the picture with "before DFS consolidation" and "after DFS consolidation".
It looks like you did access the shares the "after DFS consolidation" way. Now you are using the "before DFS consolidation" way.

"after DFS consolidation" way did work when:
-logon to domain using wired connection
-detach network cable and enable wireless

Then it works correct? If so... system (routing/firewalls etc) can find and access DFS server without problems.
please confirm

What is DFS (Distributed File System)

yes, the above is correct.

"after DFS consolidation" way did work when:
-logon to domain using wired connection
-detach network cable and enable wireless

but check the post i just written with the workaround, UsernameIssues spotted the issue 100%

actually, right now for example, im on wifi, S and M fixed (see above)... but cannot access H (homefolder):

H is mapped at \\domain.com\dfsroot\HomeFolders\gabrio > NOT working

but if i open \\servername\HomeFolders\gabrio works perfect

Where is this in the registry? i tried to lookup for the 1st key and edit but it doesn't work as i did with S and M.

Gabrio

Kaktussoft said:

\\domain.com\sharename with \\servername\sharename and works PERFECT!!!
=> what happens if you open \\domain.com in windows file explorer?

\\servername\HomeFolders\gabrio (drive H) will be created automatically on logon (through group policy).
Can you do:
ping domain.com

That works fine?

good point

\\domain.com > works fine BUT when i enter the dfsroot folder like that, i can see there are X'es on all my files, and they are not synchronized.

while instead if i access \\servername\HomeFolders\gabrio they are syncronized and look "normal".

PING works too!

C:\Users\gabrio>ping domain.com

Pinging domain.com [83.140.43.190] with 32 bytes of data:
Reply from 83.140.43.190: bytes=32 time=135ms TTL=126
Reply from 83.140.43.190: bytes=32 time=83ms TTL=126
Reply from 83.140.43.190: bytes=32 time=106ms TTL=126
Reply from 83.140.43.190: bytes=32 time=71ms TTL=126

Ping statistics for 83.140.43.190:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 135ms, Average = 98ms

sorry i need to amend what i said earlier, the H drive behaves differently than the S and M did, those i couldnt really access, the H here instead (the problematic home folder), opens but files are NOT synchronized.