Ask the Experts

[joshtseng]

Yes, \\<origin-server>\<share-name> is the correct convention.

Josh

[prh]

Am I correct in assuming the \\<origin-file-server>\<local-name> is the source file server and the share-name or is there some other reason the words "local-name" are used?  I've not been able to get any clarification on this part of the documentation.  \\<origin-file-server>\<share-name> would have been much clearer if that's what is meant.  If that's not what is meant, than can anyone present an example of what to put here?

[bgilbert]

Disregard my last post. I just realize you were asking about CIFS prepop and not PFS!

Some suggestions for gettings CIFS prepop going:

1. Verify that you have a local administrator account for accessing the prepopulation shares. You must use the correct syntax for the administrator login name even if you belong to a subdomain. For example:

admin_user@parent_realm

Do not use guest or anonymous access

2. Verify your syntax when specifying the path to the origin file server. Please use:

\\<origin-file-server>\<local-name>

3. Please verify that SMB signing is not used. Otherwise, you will have to use Riverbed's RCU utility to prepopulate.

Again, if the above doesn't work, please file a support ticket with Riverbed and have logs available.

Thanks,

Bob

[bgilbert]

Hi Erin,

Is the problem that the PFS facility will not connect to the domain? Do you get an error and/or a log entry that gives you more information? A few things to check for...

1. Before you enable PFS, configure the Steelhead appliance to use NTP to synchronize the time. To use PFS, the Steelhead appliance and the domain controller's clocks must be synchronized.

2. Make sure the client-side Steelhead appliance running PFS is running the same RiOS software version as the server-side Steelhead appliance.

3. PFS traffic to and from the Steelhead appliance travels through the Primary interface. PFS requires that the Primary interface is connected to the same switch as the LAN interface.

4. Please make sure that the PFS share and the origin server share named DO NOT contain unicode characters.

If you still have troubles with PFS registering with the domain, I suggest you open up a support ticket with Riverbed and have logs ready that cover the time when PFS is attempting to register with the domain.

Once PFS is successful in registering and you have shares setup, don't foget to use the following syntax when accessing PFS shares from a client:

//<Steelhead appliance hostname>/<share name that you gave the share in the PFS setup>


Bob

[ewoodcock]

I am trying to get my CIFS prepopulation shares set up with no luck.
I have a single domain and want to connect to \\server\data on mydomain.
I have tried every combination of \\server.mydomain.com\data to \\ip address\data, etc with no luck. Through a telnet session from the Steelhead, I have been able to ping the server via server.mydomain.com so I know it's resolving the DNS correctly.
I have also tried a lot of username combinations mydomain\user, user@mydomain.com, local admin account, etc. also with no luck.

I think I have the SMB signing turned off and loaded the RCU client service with no change.

Does anyone have any suggestions.
Thanks