Unable to reach Internet on SBS 2003 R2 domain.

I have a 2 NIC SBS 2003 R2 setup. Comcast Modem >> SBS 2003R2 Server >>> Dell Switch >>> Clients
The following clients have internet access: XP Pro Machines, iPhones, T-Mobile phones (through WiFi), etc etc.
My three new Windows 7 Pro machines can access all local resources, shares and printers BUT Can Not reach the internet.
I have no ISA running. I have run all the usual fixes such as IPCONFIG /flush dns, etc. I am very experienced and am totally at a loss for this issue. I even bought an additional 5 client / device access lic. and that did not resolve the issue...
It is only my Windows 7 Pro machines having a issue...
The one work around I have put in place is I have a block of 5 static public IP addresses. I can assign one of those addresses to point to the local (internal) ip address assigned by DHCP and the machine will then have access to the internet. I don't
like doing it this way and I should not have to...

Is the SBS server your gateway? If you do an ipconfig /all do you see the correct gateway IP address listed?
What does the network icon look like in the notification area? Is there a warning?
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Similar Messages

I can't add my Widows 7 Professional to my SBS 2003 R2 Domain

I am working on a Windows 2003 R2 Small Business Systems network, with 6 Windows Vista computers already attached to its domain. I am trying to add a Windows 7 Professional laptop to this domain, but have not been able to make that addition, even though
I have tried several of the fixes I have found on different forums. I have run the KB926505 patch on the server, tried adding the computer through the sever addition process then tried to add it from the computer. All efforts have failed. When using the server
set up, I am told that a script will run to complete the process, but that never happens. When I try to add the computer to the domain from the computer, I get an error that says it can't find the domain controller, even though I can ping the IP of the server.
The text from the "dcdiag.txt" file is -> DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "pinnaclesalesinc.local":
The query was for the SRV record for _ldap._tcp.dc._msdcs.pinnaclesalesinc.local
The following domain controllers were identified by the query:
(no Active Directory Domain Controllers found)
However no domain controllers could be contacted.
Common causes of this error include:
- Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or are not running.
Any help would be greatly appreciated.

On the laptop go to the command line and run ipconfig /all to make sure the laptop is getting its IP info from the SBS2003's DHCP and verify DNS is pointing to the SBS2003 server. The DNS server on the laptop needs to point to the SBS server and
not some other DNS in order to retrieve that record. If it is OK then maybe check that the record exists in the SBS2003 DNS or run the SBS2003 BPA (http://www.microsoft.com/en-ca/download/details.aspx?id=5334) as I believe it will check for that.
-- Al

Migrate SBS 2003 with AD and Exchange to Windows Server 2012 Standard

We are using SBS 2003 and we have configured Exchange server and AD with DNS and DHCP. Now we are planning to move SBS 2003 to Separate servers like windows server 2012 standard AD with DNS and DHCP and Windows server 2012 Standard with Exchange
2010.
Is it Possible?? we need step by step guide.
Thanks in advance.

Hi,
You probably would not find any step by step guide for this kind of migrations. If you are not comfortable with doing such migrations I would recommend to if you need to do it your self do some test migrations. Or otherwise get help by a local IT company
that is familiar with migrations.
But to give you some information, first thing before starting a migration is check the health of your SBS 2003 server / domain. Use tools like dcdiag, netdiag and best practice analyzer. I wrote a blog post about steps to think about before you start this
might help: http://blog.ronnypot.nl/?p=914
When every thing is clean you can start adding the new windows server 2012 machines as member servers to your domain.
Next you can promote one of the servers to additional domain controller on your domain (Keep in mind SBS needs to hold all FSMO roles so moving these is the last step your should do.) Also promoting a windows server 2012 to domain controller has slightly
changed, you need to install the ADDS role and follow the wizard to promote the server to a DC.
With installation of the new DC install DNS allongsite it will automatic replicate settings during confiugration.
DHCP must be installed manual, depending on your scope and settings it might be as easy to create a new scope and disable the old dhcp server.
On the server Exchange needs to be installed, make sure you install and do all pre-requirements. Than install Exchange it will automaticly detect you already have an Exchange organization and is installed as additional server. You can configure all settings
and when everything is configured right you start moving mailboxes.
When everything is moved away from the SBS 2003 server, uninstall exchange, move the FSMO roles to the new DC and after that demote the sbs 2003 server so it is not listed anymore as an additional DC in the domain. Last would be shutdown the server and remove
all records left in AD and DNS.
There is this guide for migrating SBS 2003 to windows server 2008 R2 and Exchange 2010, this might give you some usefull information, not everything will be the same but it is a good start:
http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
Regards Ronny
Visit my Blog or follow me on
Twitter

"Unable to Reach Servers" and "Connect to the Internet" Error Messages

Hi.
So, I purchased Adobe Audition at $19.99 per month for a year.
It hasn't worked yet.
I've tried all the online forum advice - drop firewall, check hosts file, check some certificate, remove/reinstall Audition ...nothing has worked. I still get messages saying "Unable to Reach Servers" and "Connect to the Internet." I'm ALWAYS connected to the Internet.
I use Windows 7 Home Premium SP1, 64-Bit operating system.
This needs to be fixed, or I want my money back.
Someone please help. I'm already 2 days with no access to something I've paid for. I don't like this.
-Karen

Karen did you have any questions regarding the steps listed in Sign in, activation, or connection errors | CC, CS6, CS5.5 - http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html. If your membership is valid then there must be a connection error between the computer and our activation server.
Are you on a managed network? Do you utilize a hardware firewall or proxy server?

Conecting to the internet Via a SBS 2003 Windows server

I have 2 macs connected through a 10/100 tbase switch and a SBS 2003 windows server also connected to the switch. The widows server is what accesses the internet. how do i get the macs to pick up the conection???

Hi, and a warm welcome to the forums!
http://www.chicagotech.net/icssetup.htm
http://support.microsoft.com/kb/324286
http://www.ifelix.co.uk/tech/index.html

SBS 2003 SP2: VSS errors; unable to create system state backup (NTBACKUP)

NTBACKUP system state on W2k3 server fails after "thinking" for ~10 mins and "creating" shadow copy; almost no disk activity, almost no CPU load. Errors in the Application
log:
Source: SQLVDI EventID: 1
Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3392. Thread=29348. Client. Instance=. VD=Global\{9B35142B-C687-4766-9707-BC387534BA38}1_SQLVDIMemoryName_0.
Several of them.
Then:
EventID: 8019
Source: NTBackup
End Operation: Warnings or errors were encountered.
Consult the backup report for more details.
Then:
Source: VSS
EventID: 12305
Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9,0xc0000000,0x00000003,...).
And finally:
EventID: 12293
Source: VSS
Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PostFinalCommitSnapshots({de0d580b-68ce-4eae-a046-b5b5b7a80235}, 1) [hr = 0x80042308].
When creating shadow copy on the system volume, the operation may take ~40-90 mins. On the data volume -- <1 min.
"vssadmin list writers" shows:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'SqlServerWriter'
State: [10] Failed
Last error: Retryable error
Writer name: 'MSDEWriter'
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'NTDS'
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Event Log Writer'
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Certificate Authority'
State: [10] Failed
Last error: Retryable error
Writer name: 'WINS Jet Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Registry Writer'
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
State: [1] Stable
Last error: No error
Writer name: 'TermServLicensing'
State: [10] Failed
Last error: Retryable error
Writer name: 'WMI Writer'
State: [10] Failed
Last error: Retryable error
Here is what I tried to do:
1. Restarted that thing.
2. Cleaned the security log.
3. Installed Windows Server 2003 Hotfix rollup KB940349-v3.
4. Stopped both SBSMONITORING and SHAREPOINT instances of MSDE, SQL 2005, SQL 2005 VSS and tried to perform the system state backup then. Stopped Exchange 2003 before launching NTBACKUP as well.
5. "regsvr32 sqlvdi.dll" in MSDE directory.
6. Renamed "System Volume Information" on all volumes and VSS has re-created them.
7. chkdsk /f was fun on all volumes, no major issues found.
8. Installed Hotfixes KB967551, KB975928-v2 (someone recommended).
9. Disabled SQL Server VSS Writer (SQLVDI errors disappeared from the application event log, VSS and NTBACKUP errors stayed).
10. Re-registered the DLLs as per Shaon Shan's post at http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/346fa42c-a476-457f-bcf3-59f87e444b55
The above had no effect on the issue whatsoever, except a little change at item 9 as mentioned.

Hi there.
I just had that problem. I saw friday my backup from my sbs 2003, was not completing becasuse it said it couldn´t creat a shadow copy in the external drive... It kept giving me errors os VSS and Volsnap... But strange thing is, i have VSS turned off in all
drives, and from months no problems with backups... So i went in Event viewer and look at it with attention, i saw a error that keep coming up from time to time (because we change the external drive form week to week). And i realize that there's a disk error
event...
Couldn´t run checkdisk from server, dont now why.. So i disconnected the drive, connected to my laptop, and ran a CheckDisk /F /X. ... It had BAD SECTORS! So i ran check disk... waited like 10-20 minutes. And then i ran it again just in case, and the 2nd
time was much more faster, like 3-6 minutes.
I disconnected from laptop, and connected to server. I went to the Backup wizard (in server managment), and press Backup now...
It hang 5-10 second in Creating Shadow copy..... And it started making the Backup :_D
I've seen all errors that were reported exactly as mine. I ran the Hotfix, all stayed the same, i followed all manual steps and still the same... and the problem was always in the external drive, which had bad sectors.
Hope it will help the next person that needs this info!

SBS 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

SBS 2003 R2 premium (with ISA 2004) Exchange ActiveSync not working

A client has a SBS 2003 R2 premium (with ISA 2004) and wants to sync iPhones and Android phones.
When using the Microsoft Remote Connectivity Analyzer and selecting 'Exchange ActiveSync' we get 'The test of the FolderSync command failed. Exchange ActiveSync returned an HTTP
500 response.'
We tried every solution we could find on the internet, without success.
This is what we tried and checked so far:
- fixed IP, DNS, trusted SSL (comodo) seem all OK
- Exchange 2003 SP2 and ISA 2004 SP3 installed.
- RWW and OWA working fine.
- tests with iPhone and Android -> 'cannot get mail. The connection to the server failed'.
- event viewer reveals no further clues.
- ran CEICW several times enabling and disabling most remote options (OWA OMA,...)
- manually checked all vDir settings in IIS6
- tested with different accounts, created a testaccount without any administrative privileges in Active Directory.
- surfing to servername/microsoft-server-activesync from local network and to domain/microsoft-server-ActiveSync from external computer both give: HTTP 501/HTTP 505 error as expected.
- reset the default virtual directories
- on ISA a query by dest port (443) shows traffic reaching the ISA server ending in:
Log type:
Web Proxy (Reverse)
Status:
500 Internal Server Error
Rule:
SBS OMA Web Publishing Rule
Source:
External ( XX.XX.XX.XX:0)
Destination:
( XX.XX.XX.XX:443)
Request:
POST
Filter information:
Req ID: 1c6d0bea
Protocol:
https
User:
anonymous
Could anyone give me any pointers on what I need to do to get this working please?
Many thanks in advance for your assistance.
Regards
Jean-Paul Laffargue
ARCOM BVBA

I used to have a SBS2003 on ISA running activesync with no issues so I'll try and give you guidance although it's been a while. I gather this is the first time use of this feature on this SBS? If so make sure you follow the instructions here:
http://technet.microsoft.com/en-us/library/cc182239.aspx
Also make sure you've enabled all mobile services in exchange features and updated your users with the Mobile User profile (I think they need to be members of the Mobile and Remote Web Workplace groups in Manage Users IIRC). Anything in the event logs?
Also, for some phones you need to manually download the certificate if you use a self-signed type.
Note that in the end it may be time to replace this soon to be unsupported ISA with a separate firewall (or a "free" Untangle box) and go to a one NIC solution. It simplifies things and you need to do that anyway to transition off SBS2003 when it is
unsupported next year.
-- Al

Unable to reach Adobe servers, Please check firewall settings and try again

I have been a creative cloud customer since it started and I've never experienced such buggy software as the app manager. The customer experience is just shocking and I wish Adobe would just offer direct downloads for the software we need rather than use the app manager.
I'm currently trying to install the latest versions of the programs but the app manager keeps showing "Unable to reach Adobe servers, Please check firewall settings and try again in a few minutes".
I do not have any firewalls on my network.
I've uninstalled all previous versions of the applications.
The app manager will download a few % and then the message appears again. I click retry and it downloads another few % before showing the message again. I keep doing this until the program is fully downloaded and installed which take hours. Because I am able to eventually download the app, the error should be anything to do with my setup or internet connection as I've never had this issue before when installing adobe products.
Is there a way we can bypass the app manager and install the programs directly? This is getting very annoying and I just need my apps to install without wasting days clicking the retry button.

I'm having the exact same problem. Photoshop is stuck at 0%.
Have the links for direct download changed? When I went to http://prodesigntools.com/adobe-cc-direct-download-links.htmland then scrolled down the page to:
Photoshop CC 2014 (64-bit)
740 MB
File 2
801 MB
File 1
and then clicked on File 1 and File 2, I reached a page that says "You don't have permission to access "http://trials3.adobe.com/AdobeProducts/PHSP/15/win64/Photoshop_15_LS20_win64.7z?" on this server."

Windows 7/SBS 2003 Networking Issue complicated by Verizon Router

I posted on Answers.Microsoft.com ( http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/windows-7-suddenly-wont-talk-to-sbs-2003-server/e8116774-6b4f-44d3-91cf-b10df236805a?tm=1405553282721 ) and here at TechNet in the Windows 7 IT Pro
forum ( http://social.technet.microsoft.com/Forums/en-US/1f8b8cbc-4b9d-4f68-981c-4c71e7a3f24a/windows-7-suddenly-wont-talk-to-sbs-2003-server-and-viceversa-possibly-dns-but-not-definite?forum=w7itpronetworking ) a problem that I was having with our Windows
7 computers suddenly losing connectivity to our SBS 2003 server. Someone posted an answer (rebooting our router), which worked, but only on a temporary basis. After turning off the router and turning it back on, we get connectivity back for about 3 days, then
we lose it again, and we have to reboot the router again.
I called Verizon, and the tech I spoke to claims that the problem is that the SBS 2003 server should not be the DNS and DHCP server for the network - the Verizon router should be. He's claiming that the fact that we have IP Address Distribution turned off
on their router means that the router never properly knows where each address is assigned. The fact that this all worked up until a week or so ago, and that it's only the Windows 7 machines that are affected, he doesn't have an answer for.
His suggestions were either A) turn off DNS and DHCP on the SBS 2003 server and have both run through the Verizon router, or B) assign static IP addresses to each machine. From what little I know (I inherited this system from someone who left little or nothing
in the way of technical notes) DNS and DHCP have to be running on the SBS 2003 server since it is a domain controller. B) seems possible, as long as I note the static addresses both on the server and on the router.
This still, however, does not really address the underlying issue. Somehow, I think there should be another, easier way to make this work. Especially since, as I said, these Windows 7 machines were content to run for about a year, and only in the past week
or two started having this issue.
Any help would be greatly appreciated.
============== Brian Gerstel Billing and IT Support, Regional Bankruptcy Center of Southeastern PA, P.C.

The LAN is all one subnet (it's not a very big office), a 192.168.1.X network.
I don't think the router's firmware has been updated recently, although I can't swear to what Verizon might have done "behind my back" (they do funny things with some of their routers, from what I can tell),
The router doesn't sit between the server and the clients - it only links our LAN and WAN (there's 1 port on the router hooked to the uplink port of a 16-port Gigabit switch which handles the LAN).
The router is the default gateway for all the systems on the LAN.
When the Windows 7 problem occurs, a Windows XP client can ping a Windows 7 client and vice versa, but a Windows 7 client can't ping the SBS server nor vice versa (and in all cases, I'm pinging numeric IP addresses, not the name). Since the SBS server is
the DNS server, the Windows 7 clients effectively lose the ability to go out on the Internet, although some programs that must cache the data (like Microsoft Outlook) seem to continue working so I think WAN access is still up for them.
Brian Gerstel Billing and IT Support, Regional Bankruptcy Center of Southeastern PA, P.C.

Mac Mini unable to reach NAS while MacBook Air can

Hi Everyone,
I've got an issue with my LAN. One computer on the LAN, a Mac Mini, is unable to reach the NAS even though all other devices can.
The setup is nothing exotic. It's a home wifi router from my local telco provider. On the Cabled interface I have a NAS, on the Wifi side I have several devices amongst which a Mac Mini and a Macbook Air. All IP addresses are handed out through DHCP. The DHCP server is set to assign a fixed address to both the NAS and the Mac Mini.
The Macbook and the Mac Mini can see each other just fine, the Macbook can access the NAS but the Mini can not. The Mini has no other issues to speak of, it can access everything else just fine.
The issue appears intermittent but I have not found a pattern. Rebooting the NAS, Mini or router individually had no effect. Below is a log of commands and output from the mac mini.
What should I be looking for to troubleshoot this appropriately?
[admin@htpc] ~ $ system_profiler SPSoftwareDataType
Software:
    System Software Overview:
      System Version: OS X 10.8.4 (12E55)
      Kernel Version: Darwin 12.4.0
      Boot Volume: Macintosh HD
      Boot Mode: Normal
      Computer Name: HTPC
      User Name: admin (admin)
      Secure Virtual Memory: Enabled
      Time since boot: 25 minutes
[admin@htpc] ~ $ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
        ether 10:9a:dd:6d:8b:b7
        media: autoselect (none)
        status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 10:9a:dd:ba:d4:96
        inet6 fe80::129a:ddff:feba:d496%en1 prefixlen 64 scopeid 0x5
        inet 192.168.1.19 netmask 0xffffff00 broadcast 192.168.1.255
        media: autoselect
        status: active
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
        lladdr 70:cd:60:ff:fe:5a:f2:30
        media: autoselect <full-duplex>
        status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
        ether 02:9a:dd:ba:d4:96
        media: autoselect
        status: inactive
[admin@htpc] ~ $ arp -a
livebox.home (192.168.1.1) at 3c:81:d8:d7:bc:a4 on en1 ifscope [ethernet]
lightmac.home (192.168.1.15) at 10:93:e9:7:a8:66 on en1 ifscope [ethernet]
droboshare.home (192.168.1.20) at 0:1a:62:0:7:ce on en1 ifscope [ethernet]
? (192.168.1.255) at ff:ff:ff:ff:ff:ff on en1 ifscope [ethernet]
[admin@htpc] ~ $ ping droboshare.home
PING droboshare.home (192.168.1.20): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
^C
--- droboshare.home ping statistics ---
11 packets transmitted, 0 packets received, 100.0% packet loss

Hi Linc,
The NAS responds to pings from other devices on the network.
The Mac Mini has no other issues with regards to accessing the network or the Internet.
I'll restart the router once more to see if this has an effect, but so far no positive change.

SBS 2003 server admin rights dont work access denied on VSS and Network settings

Hi I have just taken over support for a company and have inherited a SBS 2003 Server.
The server has had no backup for over a year (when the last admin left).
VSS does not work, so the back does not work, unable to install any other backup as no admin rights.
I want to repair it so I can do a backup to move to a new server.
I did not know the administrator account password (the last admin didn't tell anyone)
So I used a password reset boot cd and then restarted Windows 2003 in Directory Service Restore Mode.
Copied SRVANY and INSTSRV to a temporary folder, mine is called D:\temp. Copied cmd.exe to this folder too. Next ran at a command prompt instsrv PassRecovery "d:\temp\srvany.exe"
next
Started Regedit, and navigated to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\PassRecovery
Created a new subkey called Parameters and added two new values:
name: Application
type: REG_SZ (string)
value: d:\temp\cmd.exe
name: AppParameters
type: REG_SZ (string)
value: /k net user administrator 123456 /domain
"123456 is substituted for the password I used" Im not daft enough to publish it lol
Next
opened the Services applet (Control Panel\Administrative Tools\Services) and opened the PassRecovery property tab. Checked the starting mode is set to Automatic.
to the Log On tab and enable the option Allow service to interact with the desktop.
Restart Windows normally, SRVANY run the NET USER command and reset the domain admin password.
OK so now I am logged in as administrator but guess what I still don't have admin rights???
I can add new user with admin rights and log in as them but they still don't have admin rights Im totally lost??????????? Help please

I'm thinking the previous tech may have renamed the built-in domain Administrator and then created a new account called 'administrator' with lesser rights? He then used another domain admin account to manage the server.
If so, and given the fact that you don't know any domain admin account usernames or passwords, I think you may be in for a move to a new server without a proper NT backup of the SBS 2003.
However, If you can at least log into the SBS 2003, I wonder if you could download and run DIsk2VHD and create VHDs (not VHDX) of the current SBS 2003 drives, saving them to an external USB drive connected to the server.
You could then 'attach' the VHDs to a Win7 Pro computer and gain access to the files/folders, although not the Active Directory stuff. Moving Exchange and Sharepoint would impose additional pain. For Exchange, you could log
onto workstations as each user and export their Exchange mailboxes as .PSTs. I believe you could do the same with any Public Folders.
Disk2VHD
http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx
How to Mount a Virtual Hard Disk in Windows 7
http://www.online-tech-tips.com/windows-7/mount-vhd-windows-7/
Of course, the owner could also have his attorney contact the previous tech and threaten legal action unless he coughs up the correct domain admin username and password. That username and password belong to the owner, not the
tech.
Merv Porter
=========================

'Download Error' due to 'Unable to reach Adobe servers'.

I am getting a 'Download Error' due to 'Unable to reach Adobe servers'. I have already reconnected and disconnected my internet, and nothing has changed. How can I fix this problem? If anyone can help, I would truly be grateful. Thanks!
- Bobby Bobface

Not really a Premiere Pro problem, so moving this to the Downloading, Installing, Setting Up forum.
Re: Receiving error stating not able to access the Internet in Adobe Download Assistant

Unable to reach Application Server. Contact your admin ( ERR WIJ 20010 )

Hi all,
When i am using web intelligence in infoview, i am getting the following error.
Unable to reach Application Server. Contact your administrator ( ERR WIJ 20010 ).
I have logged in using admin credentials.

Hi everyone.
Could I get a quick reply if this is still an issue for you all? If it is not, has anything changed in your environment. I have one person reporting this now.
Full log:
Version:12.1.8.1176
Application server:
............cdzisapi.wis
Stack trace:
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at com.businessobjects.wp.cpi.CPIConnection.postRequest(Unknown Source)
at com.businessobjects.wp.xml.XMLViaHttp.loadScript(Unknown Source)
at com.businessobjects.wp.xml.XMLViaHttp.ping(Unknown Source)
at com.businessobjects.wp.xml.XMLSession.ping(Unknown Source)
at com.businessobjects.wp.om.OMSessionLoader.ping(Unknown Source)
at com.businessobjects.wp.tc.thread.PingRunner.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
BOE 3.1
Windows 2003 SP2
Tomcat 5.5.2
IIS 6
.net Framework 2
SQL Server 2005
Edited by: Terri Hoffmeyer-Ramos on Sep 12, 2011 9:57 PM

OWA is not receiving emails // SBS 2003

Hi Guys!
I have a following problem on my SBS 2003 Server, I do not receive emails when I access my mailbox with Outlook Web Access from home or any remote location. But if the outlook on my workstation is left on it is ok, mails are popping up right away on the
OWA too.
It was working great for me for many years.
I looked over the internet but nothing seemed to help yet...
I deleted and then created new .ost file, I have cashed mode switched off, I deleted forwarding rule that I had to my private account.
Do you have any ideas what might cause this?
Any help would be appreciated!

Most interesting. From the sound of it your Outlook is somehow set to trigger the release of mail into the Exchange server, which I have never seen. Whether SMTP or POP3, mail should arrive at the Server and OL or OWA are just "windows" or "periscopes" to
allow viewing. Is it possible that your Outlook is popping for the mail and the default mailbox is the Exchange server?
For your home copy of OL, consider Outlook Anywhere instead of VPN. VPN's are old school and expose your business network to any nastiness that creeps into your remote systems. You will find instructions on the RWW landing page.
For SMTP... you should have a static IP at the office, forward port 25 from your edge device/firewall/router to the ip of your SBS, then change your MX record at your public DNS host to point to your public IP (some use A records for the IP and the
MX points to the A record, some use IP numbers, check with your DNS host), then run the CEICW wizard specifying SMTP mail.
As for mail getting lost or something going wrong.... yes it can. But so can POP3. Historically there have been more issues with POP3 than SMTP. Consider that only the smallest of the organizations would use POP3, that every business larger
than those in the SBS space uses SMTP and you get the idea. SMTP is "store and forward", meaning if your system is off line for some little time the mail will still come. Usually it will not be returned to sender for about 48 hours, which is sufficient
time to get the SBS back on line or to change the MX record back until it is. There are also web services that will act as backup mail servers and hold your mail, some that will allow "Web Mail" access to it, and some that will do both and are very low
cost or even free.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

Unable to reach Internet on SBS 2003 R2 domain.

Similar Messages

Maybe you are looking for