[dba-SQLServer]SQL server on VLAN, in own workgroup

Eric Barro ebarro at afsweb.com
Thu Aug 21 10:32:31 CDT 2003


Look for your HOSTS file and put an entry in for the remote SQL server machine like...

xxx.xxx.xxx.xxx	RemoteSQLServer

where xxx.xxx.xxx.xxx is the IP address

SQL server can be set to listen to named pipes (using UNC ex. \\MYSQLSERVER\....) and/or via TCPIP at port 1433 (standard).

If you are using mixed authentication (Windows and SQL) make sure you have a Windows account on the domain where the SQL server is. If not use SQL server login.


---
Eric Barro
Senior Systems Analyst
Advanced Field Services
(208) 772-7060
http://www.afsweb.com 

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Lavsa,
Rich
Sent: Thursday, August 21, 2003 8:05 AM
To: 'dba-sqlserver at databaseadvisors.com'
Subject: RE: [dba-SQLServer]SQL server on VLAN, in own workgroup


Ok.. finally got answer...

There is no firewall between main office and sites.  

I've never made connection using the Client Utility... I'll give it a try.. 

I was thinking.. I can ping the machine.. so I know its on the network.  I
however cannot see the computer through "network neighborhood".  Now when I
try to register the server it asks for a name and password, I give it the SA
name and put in the correct password.  Now at this point, how does it know I
have any permission to view the contents of that server, meaning a login and
permissions set so that as an administrator I can install, maintain.. etc.
Am I to assume that I am trying to gain access to that domain using the
login name from the domain I am coming from?  Do I need to setup a local
account on that machine or something.

If so how do I get around this.. my network people are very very incompetent
so please bear with me.. I'm trying to eventually wear that hat too.. but
I'm just to busy to get into all that right now. 

Rich

-----Original Message-----
From: Haslett, Andrew [mailto:andrew.haslett at ilc.gov.au]
Sent: Thursday, August 21, 2003 8:34 AM
To: 'dba-sqlserver at databaseadvisors.com'
Subject: RE: [dba-SQLServer]SQL server on VLAN, in own workgroup


OK.

Perhaps a library configuration issue?

Perhaps try creating your connection through the Client Utility (named
pipes/TCP/etc..)

Seems strange that you can PING it though...

Wouldn't be as simple as that server not being run in mixed mode??  As you
wouldn't be able to use Windows Auth across domains..


-----Original Message-----
From: Lavsa, Rich [mailto:Rich_Lavsa at pghcorning.com]
Sent: Thursday, 21 August 2003 9:58 PM
To: 'dba-sqlserver at databaseadvisors.com'
Subject: RE: [dba-SQLServer]SQL server on VLAN, in own workgroup


I went to the highest level using the SA login just to make sure it was not
the login at least at the sql server level.  I'm not sure if its as simple
as me not having the appropriate permissions on that server itself.  

I will check on the firewall, however I do not think there is a firewall
between sites, just between us and the rest of the world.  

This workgroup was set up by the consultants not our staff.  I'm not a
network guy so I'm not sure if our network guys need to do anything to allow
me to see this.. I wish they would just put it in our domain.  

I'll find out about the firewall and get back to you.

-----Original Message-----
From: Haslett, Andrew [mailto:andrew.haslett at ilc.gov.au]
Sent: Thursday, August 21, 2003 8:13 AM
To: 'dba-sqlserver at databaseadvisors.com'
Subject: RE: [dba-SQLServer]SQL server on VLAN, in own workgroup


Are you trying to connect using integrated auth. or SQL auth.

Do you have a firewall in between the LANS that could be blocking the
required ports? 1433 I think...

Cheers,
Andrew



-----Original Message-----
From: Lavsa, Rich [mailto:Rich_Lavsa at pghcorning.com]
Sent: Thursday, 21 August 2003 9:41 PM
To: 'dba-sqlserver at databaseadvisors.com'
Subject: [dba-SQLServer]SQL server on VLAN, in own workgroup


Hello all,

I have a situation.. 

Setup is Win2K desktop, Win2k SErvers (mix mode Active Directory), SQL
SErver 2000.

The company I work for has a main office in Pittsburgh, and 2 manufacturing
plants (one in Port Allegany, PA, and one Sedalia, Missouri).  We are
connected VIA a WAN.  In our Port Plant, we are implementing new technology
to gather defect information from the plant floor.  This information will be
held in a sql server database.  The software company recommends this system
be separated by a VLAN which has been set up and is working.  They also
recommend having this sql server, PLC, and 2 other machines be exclusively
on their own network of which a workgroup was set up.  I'm not a network
kind of guy, know enough to get around but that's about it.  

So now I'm the SQL server person here.  I'm new to it, learning it as I go
with a 5 day class under my belt.  We have quite a few sql server database
servers doing various things, all of which I have taken responsibility for.
I connect to all of them using Enterprise Manager on my machine.  I cannot
connect to the new SQL server that is on the VLAN.  I can ping the server,
however using the IP address I cannot register the server with my Enterprise
Manager.  

Has anyone done this, or know how to do this?

Rich
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

IMPORTANT - PLEASE READ ******************** 
This email and any files transmitted with it are confidential and may 
contain information protected by law from disclosure. 
If you have received this message in error, please notify the sender 
immediately and delete this email from your system. 
No warranty is given that this email or files, if attached to this 
email, are free from computer viruses or other defects. They 
are provided on the basis the user assumes all responsibility for 
loss, damage or consequence resulting directly or indirectly from 
their use, whether caused by the negligence of the sender or not.
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

IMPORTANT - PLEASE READ ******************** 
This email and any files transmitted with it are confidential and may 
contain information protected by law from disclosure. 
If you have received this message in error, please notify the sender 
immediately and delete this email from your system. 
No warranty is given that this email or files, if attached to this 
email, are free from computer viruses or other defects. They 
are provided on the basis the user assumes all responsibility for 
loss, damage or consequence resulting directly or indirectly from 
their use, whether caused by the negligence of the sender or not.
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.509 / Virus Database: 306 - Release Date: 8/12/2003

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.509 / Virus Database: 306 - Release Date: 8/12/2003




More information about the dba-SQLServer mailing list