Have a couple of questions, I just installed a new server with 2012 on it, and all of the other workstations have windows 8 pro, but they are wireless, The server is hooked into the wireless network, can i just have them join the domain? and what is the proper setup for integrating a sonicwall firewall, is it modem firewall router than switch? I can't seem to get the firewall to deploy,
Question about a new network
- Thread starter zlawson13
- Start date
Solution
SolianHelix
Honorable
- Aug 1, 2013
- 21
- 0
- 10,540
As long as you can ping each workstation from the server, you should have no problem creating and adding the workstations to a new domain.
To create a new domain in Windows Server 2012, open the Server Manager and select "Local Server". Then click on the temporary computer name. Select change, then give the server a valid name. Then under 'Member of', select the Domain radio button and add a new Domain Name.
Installing Server 2012 and Creating Domains
Also, this link may help you with your SonicWALL issues: Creating and Deploying the default .RCF
SolianHelix :
As long as you can ping each workstation from the server, you should have no problem creating and adding the workstations to a new domain.
To create a new domain in Windows Server 2012, open the Server Manager and select "Local Server". Then click on the temporary computer name. Select change, then give the server a valid name. Then under 'Member of', select the Domain radio button and add a new Domain Name.
Installing Server 2012 and Creating Domains
Also, this link may help you with your SonicWALL issues: Creating and Deploying the default .RCF
Alright, its been a mess I thank you for your help, i hope this works,
choucove
Distinguished
- May 13, 2011
- 756
- 0
- 19,360
Deploying the Sonicwall Firewall depends upon what devices you currently have doing what role in your network. If you have a modem that is connecting back to your ISP, then you're going to connect your Sonicwall behind that, to act as your primary network router. X1 interface is the WAN, while by default X0, X2, X3, and X4 are all part of the LAN network. You will connect your switch behind the Sonicwall to one of the LAN ports.
After you have built your primary domain controller, don't forget that on each workstation computer you must set the primary DNS Server IP address as the IP address of your domain controller server. You can do this one of two ways. First, you can set each computer up with a static IP address in Windows, ensuring that no two computers have the same IP address, and statically assign the Primary DNS Server to the IP address of your domain controller. Or, you can set the IP address of your domain controller as the Primary DNS Server in your DHCP server, whether that is being used on the Sonicwall or directly on the new server. This way when a computer connects to the network and requests an IP address from the DHCP server, it is being handed the IP address of your domain controller (and DNS server) as the Primary DNS Server address.
If that is in place, then you can start joining computers to the domain. I'd recommend in your Active Directory Users and Computers to create a new Organizational Unit to create all your network users and computers, instead of using the pre-configured Users and Computers folders. This is to help with applying group policy objects (GPOs) in the future as needed.
After you have built your primary domain controller, don't forget that on each workstation computer you must set the primary DNS Server IP address as the IP address of your domain controller server. You can do this one of two ways. First, you can set each computer up with a static IP address in Windows, ensuring that no two computers have the same IP address, and statically assign the Primary DNS Server to the IP address of your domain controller. Or, you can set the IP address of your domain controller as the Primary DNS Server in your DHCP server, whether that is being used on the Sonicwall or directly on the new server. This way when a computer connects to the network and requests an IP address from the DHCP server, it is being handed the IP address of your domain controller (and DNS server) as the Primary DNS Server address.
If that is in place, then you can start joining computers to the domain. I'd recommend in your Active Directory Users and Computers to create a new Organizational Unit to create all your network users and computers, instead of using the pre-configured Users and Computers folders. This is to help with applying group policy objects (GPOs) in the future as needed.
choucove
Distinguished
- May 13, 2011
- 756
- 0
- 19,360
Have you configured the Sonicwall to the proper network settings for your deployment? You will have to connect the Sonicwall to a computer, set it to a static IP address (the default static IP of the Sonicwall is 192.168.168.168) and log in to configure the Sonicwall with the pertinent network information.
If you have configured the Sonicwall, what settings did you use? What is your IP address scheme, and how is everything connected specifically?
If you have configured the Sonicwall, what settings did you use? What is your IP address scheme, and how is everything connected specifically?
Yeah I have access to that but no Internet when I hook it up. .. my wiring with the firewall is modem plugged into wan lan connected to the router upload port. Where the modem plugin used to go. And another lan connected to the server. . I can access the 192.168.168.168 but once I'm in kinda lost.
choucove
Distinguished
- May 13, 2011
- 756
- 0
- 19,360
Your router will no longer be connected like this. It's going to only be used as a Wireless Access Point, and will connect to your primary switch to a LAN port on the router, not the WAN. I don't know for sure what IP address scheme you are wanting to use, but I'll give an example below and you can set the IP address information then to what you want.
SONICWALL TZ 105
-------------------------
Interface X0:
Zone - LAN
IP Address: Static 192.168.5.1
Subnet Mask: 255.255.255.0
DHCP Server: 192.168.5.50 - 100
Primary DNS Server: 192.168.5.253 (the IP address of your Domain Controller/DNS server)
Secondary DNS Server: 8.8.8.8 (or the IP address of your ISP's DNS server)
Interface X1:
Zone - WAN
IP Address - DHCP (will be assigned an IP address by the modem. If you don't want this, and know the IP address range your modem is in, assign a static IP address in that range.)
Interface X2, X3, X4:
Portshield Mode to LAN Zone (this makes them basically switch ports on the same LAN network as X0 interface.)
Once these settings are done be sure to do a restart on the firewall so that the running configuration is completely saved. Now to connect the other devices. You will plug Eth1 port of your primary switch into the X0, X2, X3, or X4 port on the Sonicwall. They all go to the same network, so any one of those interfaces should be fine for now. Connect up your wired connections to your primary switch, and you will also plug in your wireless router to the switch. Connect the switch to LAN port 1 on your wireless router, not the WAN port. Your router will no longer be doing any routing, and will act basically like a wireless antenna for your existing network which is now managed and routed by the Sonicwall. You will want to configure the IP address settings of your wireless router by logging into it's configuration page. You will probably need to first access to the IP address of what was previously your default gateway (often times 192.168.1.1) to get into the original configuration of the wireless router. From there you can change the IP address information and other necessary settings.
WIRELESS ROUTER
------------------------
IP Address: 192.168.5.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.5.1
DHCP Server: DISABLED (your Sonicwall currently is running DHCP, not the wireless router.)
Again, be sure you save and reboot your wireless router to ensure that you have saved the settings. You should now be able to connect devices onto your wireless network. If you are using Static IP addresses on your computers, set them up in the 192.168.5.0 network, such as the example below:
IP address: 192.168.5.10
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.5.1
Primary DNS Server: 192.168.5.253
Secondary DNS Server: 8.8.8.8
If you are using DHCP on your computers, then open up the Command Line utility (from the Start window start typing CMD and hit Enter.) Type in the following commands to release any previous IP address settings and request new IP address information from the DHCP server at the Sonicwall:
ipconfig /release
ipconfig /renew
Make sure that the IP address your computer picks up is in the 192.168.5.0 network with the other correct information. Once this is done, it's time to test and troubleshoot settings. Let me know when you get to this point and I can help out with determining what you might be running into for problems getting network connectivity if you do.
SONICWALL TZ 105
-------------------------
Interface X0:
Zone - LAN
IP Address: Static 192.168.5.1
Subnet Mask: 255.255.255.0
DHCP Server: 192.168.5.50 - 100
Primary DNS Server: 192.168.5.253 (the IP address of your Domain Controller/DNS server)
Secondary DNS Server: 8.8.8.8 (or the IP address of your ISP's DNS server)
Interface X1:
Zone - WAN
IP Address - DHCP (will be assigned an IP address by the modem. If you don't want this, and know the IP address range your modem is in, assign a static IP address in that range.)
Interface X2, X3, X4:
Portshield Mode to LAN Zone (this makes them basically switch ports on the same LAN network as X0 interface.)
Once these settings are done be sure to do a restart on the firewall so that the running configuration is completely saved. Now to connect the other devices. You will plug Eth1 port of your primary switch into the X0, X2, X3, or X4 port on the Sonicwall. They all go to the same network, so any one of those interfaces should be fine for now. Connect up your wired connections to your primary switch, and you will also plug in your wireless router to the switch. Connect the switch to LAN port 1 on your wireless router, not the WAN port. Your router will no longer be doing any routing, and will act basically like a wireless antenna for your existing network which is now managed and routed by the Sonicwall. You will want to configure the IP address settings of your wireless router by logging into it's configuration page. You will probably need to first access to the IP address of what was previously your default gateway (often times 192.168.1.1) to get into the original configuration of the wireless router. From there you can change the IP address information and other necessary settings.
WIRELESS ROUTER
------------------------
IP Address: 192.168.5.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.5.1
DHCP Server: DISABLED (your Sonicwall currently is running DHCP, not the wireless router.)
Again, be sure you save and reboot your wireless router to ensure that you have saved the settings. You should now be able to connect devices onto your wireless network. If you are using Static IP addresses on your computers, set them up in the 192.168.5.0 network, such as the example below:
IP address: 192.168.5.10
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.5.1
Primary DNS Server: 192.168.5.253
Secondary DNS Server: 8.8.8.8
If you are using DHCP on your computers, then open up the Command Line utility (from the Start window start typing CMD and hit Enter.) Type in the following commands to release any previous IP address settings and request new IP address information from the DHCP server at the Sonicwall:
ipconfig /release
ipconfig /renew
Make sure that the IP address your computer picks up is in the 192.168.5.0 network with the other correct information. Once this is done, it's time to test and troubleshoot settings. Let me know when you get to this point and I can help out with determining what you might be running into for problems getting network connectivity if you do.
choucove
Distinguished
- May 13, 2011
- 756
- 0
- 19,360
Your modem should connect to Interface X1, which is the default WAN interface. Do you have all of your services running on the same physical server, or are they running on one or more virtual machines? Basically anywhere that asks for a Primary DNS Server, you will use the IP address of your Domain Controller static IP address (192.168.1.41)
TRENDING THREADS
-
-
I swapped my mini-LED display for a $1,300 OLED monitor. Here’s what happened- Started by Admin
- Replies: 31
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 4K
-
-
[SOLVED] Windows is using Microsoft Basic Display Adapter ?
- Started by Corbin8756
- Replies: 89
Facebook
Twitter
Instagram