Question Locked

Win SBS 2003 DHCP

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, I am temporary taking over an IT task because our IT guy "left" his post. I had to reset the Sonicwall TZ-180 router because the IT guy would not give us the password that he had set (I will deal with this issue later!). Here is my network hardware setup:
1. Sonicwall TZ-180 router:
- WAN side: static IP with cable router.
- LAN side: Right now it is showing DHCP with reservation from 192.168.1.2-299. No static IPs showing on LAN side

2. Dell server running Windows SBS 2003. Using the ipconfig command at the server console, i'm seeing the followings:
- DHCP Enabled: No
- IP address: 192.168.1.10
- Gateway: 192.168.1.1 which is the router
- DNS: 192.168.1.10 which is the server
- Primary WINS: 192.168.99.204
- NetBIOS over TCP/IP: Disabled

2. All client workstations running WinXP Pro are configured with logon script to domain Mycompany.local using the server (192.168.1.10) as DHCP, DNS and WINS.

Here are my issues:

1. All five client workstations were working fine, and one morning three out of five workstations lost connection with the server. Using the ipconfig command, I'm not seeing any settings, as a matter of fact the ipconfig command does not seem to work on these three computers. Going through Control Panel/Network Connection reveals that the network settings are from the Sonicwall router DHCP. Why would this only happened to 3 out of 5 workstations who used the same logon script? Note: The employee told me that she had tried the Remote Desktop Connection that I left on the desktop during my testing. Do you think this would cause the server to treat the remote-logged workstations differently? I restarted, shutdown and restarted the workstations and continue to have the same problem. I temporary fix the problem so my employees can continue their work by assigning IP, Gateway, DNS, and WINS addresses in the client's NIC cards. I would like to go back to DHCP enabled on these 3 workstations.

2. Clearly, my IT person setup the Dell server to be used as a DHCP. Must I configure the Sonicwall router to give the server a static IP address? Since I had to reset the Sonicwall router, I am not so sure if he had set up the server with a static address. I would think it is correct to assign the server with a static IP, and let the server handle the DHCP tasks to all clients.

3. I had remote access to my office workstation from home using RealVNC. Since I reset the Sonicwall router, how can I set it up again for remote access? or should I use Remote Desktop Connection? Right now I have my accounting application installed on my workstation only, so I think RealVNC is ok, but I do want to have access to the server from home so I would think the Remote Desktop Connection via VPN to the server would be better. Your comments?

Any inputs, comments and recommendations are greatly appreciated.

Benny

14 replies

by robo_dev

First of all, you have two DHCP servers.

When you run ipconfig at the server, the DHCP setting is for it as a CLIENT, not as a server. You either need to:

a) login to the server and stop the DHCP service. Then adjust the DHCP range in the sonicwall to start at 20, so you don't hand out the .10 address to a workstation.

Or

b) turn off DHCP in the router.

Since Windows 2003 may also be your WINS server, it will work better if you use the Windows 2003 as your DHCP server. So your best bet is option b, disable DHCP on the LAN side of your router.

to be technically correct, the 2-255 is your DHCP 'scope' and any devices assigned permanent addresses from that scope get reservations from that scope.

For example on my home network my WLAN access point is given a reserved address of 192.168.0.11, based on its mac address.

Your server has a static IP address: .10 (it says DHCP disabled, which means it already has a static IP).

To use VNC, you need to:

a) setup a forwarding rule to forward the correct port (typically 5900 for VNC) to the LAN IP address of your workstation.

b) And on most routers you have to define a custom 'service' for a non-standard service (in this case VNC).

You then have configured the router to forward port 5900 to the IP address of your workstation.

http://www.realvnc.com/support/faq.html#natrouter

A VPN is more secure than VNC, but my experience is that VNC is easier to setup and will typically give you much faster response time/throughput.

by cg it

both DHCP servers will conflict with each other providing invalid domain resource addresses.

Second, whenever you make a change to the SBS server, you make the change using the wizards. Don't manually change configurations if there is a wizard for it.
See the management console.

Third. Always run the connect to internet wizard if you change anything related to networking.

Purchase the Small Business Server 2003 administrators companion. It will give you almost all the information on setup and managing a SBS 2003 network.

by churdoo

The Primary WINS setting on the SBS looks strange. I would modify that to 192.168.1.10 (the server IP) ... actually with SBS you should do this with the CEICW in Server Manager (Configure Email and Internet Connection Wizard)

1. With 2 active DHCP servers on a network, you will have issues like this. One cannot explain why 3 of the 5 workstations suddenly started getting DHCP from the sonicwall. You should not have 2 DHCP servers on the network; you should disable DHCP on the sonicwall and let the SBS handle the DHCP, and reset the workstations to "obtain automatically" from DHCP.

2. The SBS should be static IP and this is done on the server, so there's nothing you need to do on the sonicwall for this. You should disable DHCP on the sonicwall.

3. remote access. I'm not sure what exactly the sonicwall calls them, but you'll need to create several port forwards or port address translations on the sonicwall in order to restore your remote access functionality. Were you or your users using the SBS Remote Web Workplace?

Here are some common port forwards you may need to set in your sonicwall:
port 25 to your SBS LAN IP (SMTP email)
port 443 to your SBS LAN IP (HTTPS)
port 4125 to your SBS LAN IP (RWW)
port 1723 to your SBS LAN IP (PPTP VPN if you're using it)
port 5900 to YOUR WORKSTATION LAN IP (this is the VNC, and I caution you about exposing this directly on the internet like this, and if you continue against this advice, strongly recommend you use strong passwords on the VNC)

by cg it

If it is indeed disabled, enabling it now is going to cause you more problems that it's worth.

If the SBS box uses only 1 NIC to connect to the network, and DHCP service is disabled or not configured, then you are going to have to configure the SonicWall DHCP services with reservations and options.

The options you need to configure are DNS Server, Router. The DNS option needs to have the SBS box address as the first DNS address workstations look to. the second on is your ISP DNS servers.
As Robo and Churdo mention, you need to setup static port forwarding to the SBS box for RWW, SMTP [if you use SMTP or POP3] and any other services you want availble to remote users.

After you configure the SonicWall, you then run the connect to the internet wizard and imput the required information from the configurations you made.

note: workstations must first look to the SBS box DNS server to be able to log on to the network. If you list your ISP servers first, users will not be able to logon.

The reason for listing your ISPs DNS servers second is if the SBS box is down, workstations still have internet access via cached credential logon.

by bennp

CG IT, thanks for your input.

When i logged into the sonicwall router, i can see all the dynamic IPs that the box assigned to the workstations. Now, looking at the ipconfig output of the workstation, i see the DHCP, DNS, and WINS are set with the server's IP. If the server's DHCP is not running, the workstation will default to the Sonicwall router for IP, am I correct?

I notice that if I reboot the server, the sonicewall and or the workstations, the IP address seem to be the same everytime. This tell me that someone is issuing a static address to the workstations and the server itself.

by cg it

because it will result in the problems your experiencing. Clients will get addresses and information about resources that is not correct.

by bennp

Thanks for all your comments. To properly set this up, I should then:
1. Turn off DHCP on the LAN side in the Sonicwall router.
2. Do I need to assign a static IP of 192.168.1.10 to the server in the router? The server always bootup with this IP address.
3. BTW, how does the Primary WINS address assigned? I notice also that the current address does not seem to fit with the rest of the address.
4. It seems to me that the workstations always get the same IP address from the server. If I want to change the IP, how do I do that on the server?

Sorry for asking too many questions.

by cg it

if the SBS box DHCP service is running, then yes turn off DHCP services LAN side on the SonicWall router.

Yes the SBS box network card must have a static IP address. If the network card TCP/IP properties show a static address then don't change it.

WINS is not required unless you have W9X workstations. WINS is simply a way for clients to lookup resources from a LMHosts file. Not necessary and you should probably disable NetBIOS over TCP/IP on workstations.

If you want to change the IP on the server, you change it in the TCP/IP properties page of the network card. After you do that you MUST [yelling it] must run the connect to the internet wizard and choose the network card with the new address. you MUST do this. you can not, not do this.

by bennp

I will keep the DHCP on the server since i did not do make any changes to the server. The only thing i did was resetting the router. I will disable the DHCP in the router on the LAN side.

BTW, one question on the security issue. since my last IT tech left on a bad note and refused to give us the password to the sonicwall router. By resetting the sonicwall router with a new password is all I need to protect our network from any unauthorized intrusions, correct?

by robo_dev

how crafty was he?

did he know the axe was coming?

Did he use VNC before and/or VPN into the LAN?

Does your site have a static IP address?

Got wireless?

Got modems?

Resetting the router with a strong password is a good start.

If he used VNC before on a PC, change the static LAN IP address that you define for that PC running the VNC service to another address, change the default port VNC uses, and enable logging for that router rule in the router. Make sure you change all VNC passwords and that VNC is set to enable encryption.

Be sure to patch/update everthing.

If he was crafty, make sure no outbound connections are being established, no copies of VNC are 'phoning home' and all userids/passwords he knew are changed.

If he used the Windows VPN, you would want to revoke the certificate, and issue a new one, just to be safe.

If he's really, really crafty, there are wireless keystroke loggers, stealthy malware, covert cameras......

by bennp

Well, so far none from your listing are detected. I have changed the router access logon and password, and the VNC password. I will look into the keylogger issue.

by parsifal09

As I sit here reading this nightmare I just thought I would add two things after stating the majority of advice given looks spot on.

1.) It might be worth it to admit you're in over your head (or at least out of your comfort zone) and bite the bullet and get a consultant to come in and take stock of things and help get you setup properly. If it's a simple SBS2003 domain with less than ten client stations it really shouldn't take any consultant worth their salt more than a few hours to evaulate the network, discuss recommendations and implement any approved changes. All depends on how much your time and the cost of downtime is worth to you.

2.) Just had to respond to one of the comments made it was impossible to say how three of five workstations 'lost their way'. Sounds pretty simple to me, someone added a second DHCP server to the network and those three had leases that expired at the same time. Obviously there are any number of other plausible explanations but that seems simplest.

Anyhow, best of luck getting everything sorted out. Hopefully your luck with IT help picks up Benny, it's regrettable to hear that your admin just up and left without having a responsible exit plan in place with you first.

Tom

by bennp

Thanks Parifal09,

I'm out of my comfort zone otherwise I would not ask for help. However, I received great comments from all that helped me confirm my suspicion on the problem. It was my immediate attempt to prevent any issues with my last IT tech, I had to reset the router box, and set the dual DHCP servers in motion. I can simply correct this DHCP issue, and then get some additional help from a new IT tech.

It is tough to run a small business in this challenging economy, and have to deal with an unprofessional IT tech who thinks he can dictate the outcome by controlling your network. I feel sorry for the next IT tech or consultant that I will interview.

This discussion is closed to new replies.