Proper Server name

[Guest Tom]

Hello,

I recently setup a Windows 2003 R2 server and named it: business-server.

Everything is working fine except our remote connectivity. We can get

connected, but when I try to get to a network share (ex.

\\business-server\share1) it won't connect to it. Would a server name with

this format cause this problem?

Thanks,

Tom

[Guest Jabez Gan [MVP]]

Re: Proper Server name

 

No this server name would not affect it.

 

Try pinging the server name (or the IP) remotely. If pinging the server

doesn't give the IP address, please double check the DNS setting of the

client in the remote office, and also check the DNS Server on the remote

office. Make sure that a A record is created.

 

if it doesn't even ping the IP, then check the connectivity...

 

--

Jabez Gan

Microsoft MVP: Windows Server - File Storage

"Tom" <Tom@discussions.microsoft.com> wrote in message

news:F889B8FD-EB3E-4A63-9E27-9ABD24D6D535@microsoft.com...

> Hello,

> I recently setup a Windows 2003 R2 server and named it: business-server.

> Everything is working fine except our remote connectivity. We can get

> connected, but when I try to get to a network share (ex.

> \\business-server\share1) it won't connect to it. Would a server name

> with

> this format cause this problem?

> Thanks,

> Tom

[Guest Tom]

Re: Proper Server name

 

I can ping the external IP address of the network. There is a Linksys router

in-place. The Routing and Remote Access Services are running and I can

connect to the server by setting up a simple vpn connection in Windows. I've

tried several different OS's with no difference either way. It

authenticates, shows it's connected, but if I try to go the one of the two

network shares a message comes back that there is that Windows Cannot Access

that network resource. I even have the root drive shared on the server and

it gives the same message. One thing that I hadn't seen before was that it

made me create a default policy under the Routing and Remote Access Program

before I could connect. I must be missing something?

 

"Jabez Gan [MVP]" wrote:

> No this server name would not affect it.

>

> Try pinging the server name (or the IP) remotely. If pinging the server

> doesn't give the IP address, please double check the DNS setting of the

> client in the remote office, and also check the DNS Server on the remote

> office. Make sure that a A record is created.

>

> if it doesn't even ping the IP, then check the connectivity...

>

> --

> Jabez Gan

> Microsoft MVP: Windows Server - File Storage

> "Tom" <Tom@discussions.microsoft.com> wrote in message

> news:F889B8FD-EB3E-4A63-9E27-9ABD24D6D535@microsoft.com...

> > Hello,

> > I recently setup a Windows 2003 R2 server and named it: business-server.

> > Everything is working fine except our remote connectivity. We can get

> > connected, but when I try to get to a network share (ex.

> > \\business-server\share1) it won't connect to it. Would a server name

> > with

> > this format cause this problem?

> > Thanks,

> > Tom

>

[Guest Jabez Gan [MVP]]

Re: Proper Server name

 

Hmmm...

 

Yes by default all remote connections will be applied with the default

policy (and other policies). Check on that.

 

Also are you able to connect and retrieve the resources if you use the IP to

access remotely? IF yes, please check your DNS Server and make sure that

there's a A record to your server host name with the IP of the server

 

--

Jabez Gan

Microsoft MVP: Windows Server - File Storage

"Tom" <Tom@discussions.microsoft.com> wrote in message

news:A283D9F2-75DC-44F6-959A-4C57465CBEF8@microsoft.com...

>I can ping the external IP address of the network. There is a Linksys

>router

> in-place. The Routing and Remote Access Services are running and I can

> connect to the server by setting up a simple vpn connection in Windows.

> I've

> tried several different OS's with no difference either way. It

> authenticates, shows it's connected, but if I try to go the one of the two

> network shares a message comes back that there is that Windows Cannot

> Access

> that network resource. I even have the root drive shared on the server

> and

> it gives the same message. One thing that I hadn't seen before was that

> it

> made me create a default policy under the Routing and Remote Access

> Program

> before I could connect. I must be missing something?

>

> "Jabez Gan [MVP]" wrote:

>

>> No this server name would not affect it.

>>

>> Try pinging the server name (or the IP) remotely. If pinging the server

>> doesn't give the IP address, please double check the DNS setting of the

>> client in the remote office, and also check the DNS Server on the remote

>> office. Make sure that a A record is created.

>>

>> if it doesn't even ping the IP, then check the connectivity...

>>

>> --

>> Jabez Gan

>> Microsoft MVP: Windows Server - File Storage

>> "Tom" <Tom@discussions.microsoft.com> wrote in message

>> news:F889B8FD-EB3E-4A63-9E27-9ABD24D6D535@microsoft.com...

>> > Hello,

>> > I recently setup a Windows 2003 R2 server and named it:

>> > business-server.

>> > Everything is working fine except our remote connectivity. We can get

>> > connected, but when I try to get to a network share (ex.

>> > \\business-server\share1) it won't connect to it. Would a server name

>> > with

>> > this format cause this problem?

>> > Thanks,

>> > Tom

>>

[Guest Tom]

Re: Proper Server name

 

Using the IP address and then the share name is working. \\192.168.1.2\share1

Thanks for your help. I'll check the dns settings.

 

 

"Jabez Gan [MVP]" wrote:

> Hmmm...

>

> Yes by default all remote connections will be applied with the default

> policy (and other policies). Check on that.

>

> Also are you able to connect and retrieve the resources if you use the IP to

> access remotely? IF yes, please check your DNS Server and make sure that

> there's a A record to your server host name with the IP of the server

>

> --

> Jabez Gan

> Microsoft MVP: Windows Server - File Storage

> "Tom" <Tom@discussions.microsoft.com> wrote in message

> news:A283D9F2-75DC-44F6-959A-4C57465CBEF8@microsoft.com...

> >I can ping the external IP address of the network. There is a Linksys

> >router

> > in-place. The Routing and Remote Access Services are running and I can

> > connect to the server by setting up a simple vpn connection in Windows.

> > I've

> > tried several different OS's with no difference either way. It

> > authenticates, shows it's connected, but if I try to go the one of the two

> > network shares a message comes back that there is that Windows Cannot

> > Access

> > that network resource. I even have the root drive shared on the server

> > and

> > it gives the same message. One thing that I hadn't seen before was that

> > it

> > made me create a default policy under the Routing and Remote Access

> > Program

> > before I could connect. I must be missing something?

> >

> > "Jabez Gan [MVP]" wrote:

> >

> >> No this server name would not affect it.

> >>

> >> Try pinging the server name (or the IP) remotely. If pinging the server

> >> doesn't give the IP address, please double check the DNS setting of the

> >> client in the remote office, and also check the DNS Server on the remote

> >> office. Make sure that a A record is created.

> >>

> >> if it doesn't even ping the IP, then check the connectivity...

> >>

> >> --

> >> Jabez Gan

> >> Microsoft MVP: Windows Server - File Storage

> >> "Tom" <Tom@discussions.microsoft.com> wrote in message

> >> news:F889B8FD-EB3E-4A63-9E27-9ABD24D6D535@microsoft.com...

> >> > Hello,

> >> > I recently setup a Windows 2003 R2 server and named it:

> >> > business-server.

> >> > Everything is working fine except our remote connectivity. We can get

> >> > connected, but when I try to get to a network share (ex.

> >> > \\business-server\share1) it won't connect to it. Would a server name

> >> > with

> >> > this format cause this problem?

> >> > Thanks,

> >> > Tom

> >>

>

[Guest Jabez Gan [MVP]]

Re: Proper Server name

 

You're welcome. Ping back if you need further assistance ;)

 

--

Jabez Gan

Microsoft MVP: Windows Server - File Storage

"Tom" <Tom@discussions.microsoft.com> wrote in message

news:84D69A01-1603-4827-9307-3220FD3F2B94@microsoft.com...

> Using the IP address and then the share name is working.

> \\192.168.1.2\share1

> Thanks for your help. I'll check the dns settings.

>

>

> "Jabez Gan [MVP]" wrote:

>

>> Hmmm...

>>

>> Yes by default all remote connections will be applied with the default

>> policy (and other policies). Check on that.

>>

>> Also are you able to connect and retrieve the resources if you use the IP

>> to

>> access remotely? IF yes, please check your DNS Server and make sure that

>> there's a A record to your server host name with the IP of the server

>>

>> --

>> Jabez Gan

>> Microsoft MVP: Windows Server - File Storage

>> "Tom" <Tom@discussions.microsoft.com> wrote in message

>> news:A283D9F2-75DC-44F6-959A-4C57465CBEF8@microsoft.com...

>> >I can ping the external IP address of the network. There is a Linksys

>> >router

>> > in-place. The Routing and Remote Access Services are running and I can

>> > connect to the server by setting up a simple vpn connection in Windows.

>> > I've

>> > tried several different OS's with no difference either way. It

>> > authenticates, shows it's connected, but if I try to go the one of the

>> > two

>> > network shares a message comes back that there is that Windows Cannot

>> > Access

>> > that network resource. I even have the root drive shared on the server

>> > and

>> > it gives the same message. One thing that I hadn't seen before was

>> > that

>> > it

>> > made me create a default policy under the Routing and Remote Access

>> > Program

>> > before I could connect. I must be missing something?

>> >

>> > "Jabez Gan [MVP]" wrote:

>> >

>> >> No this server name would not affect it.

>> >>

>> >> Try pinging the server name (or the IP) remotely. If pinging the

>> >> server

>> >> doesn't give the IP address, please double check the DNS setting of

>> >> the

>> >> client in the remote office, and also check the DNS Server on the

>> >> remote

>> >> office. Make sure that a A record is created.

>> >>

>> >> if it doesn't even ping the IP, then check the connectivity...

>> >>

>> >> --

>> >> Jabez Gan

>> >> Microsoft MVP: Windows Server - File Storage

>> >> "Tom" <Tom@discussions.microsoft.com> wrote in message

>> >> news:F889B8FD-EB3E-4A63-9E27-9ABD24D6D535@microsoft.com...

>> >> > Hello,

>> >> > I recently setup a Windows 2003 R2 server and named it:

>> >> > business-server.

>> >> > Everything is working fine except our remote connectivity. We can

>> >> > get

>> >> > connected, but when I try to get to a network share (ex.

>> >> > \\business-server\share1) it won't connect to it. Would a server

>> >> > name

>> >> > with

>> >> > this format cause this problem?

>> >> > Thanks,

>> >> > Tom

>> >>

>>