Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

sql2K maintenance plan unable to use a shared 2K3 folder on the domain

Status
Not open for further replies.

dpsmith

IS-IT--Management
Feb 4, 2002
74
US
This might be a 2003 question not a SQL one but I'm stuck and I fear it's because I'm missing something really stupid.

Here goes:

I added a 2003 R2 server SP1 (basic install with no additional apps) to my network with a ton of storage.

All I want to do is change the directory where the Sql2K backup goes from an old 2K server to this new one.

For the past 3 years this has worked beautifully and will still work on any shared folder on the domain: \\192.168.35.40\SQLbackup

I change it in the Maintenance Plan to the new server IP# \\192.168.35.41\SQLbackup (I made a folder on the new server the same name)

It can't connect: "The network path was not found"

I can map a drive from the SQL server to that shared folder, and create files and delete them.
I can ping that server from the SQL server.
The only thing that fails is the Maintenance plan.
I even deleted the Plan and tried to make a new one but it still fails.
Google and this site had no posts on this.
I have no clue where to go with this.
The directory on the new server has full permissions for everyone...

Any ideas?
 
Can you use xp_cmdshell and do a dir of the folder?

Code:
xp_cmdshell 'dir \\192.168.35.41\SQLbackup\'

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
I was reading my past posts and see I never said what the problem was.

The DNS entry on this new 2003 server was pointing to the ISP's DNS server not the domain's.

After that adjustment everything was fine.

Thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top