Thank you for this...Commodore 64 was one of my favorite computers. Started with Vic-20 and after the C64, went Amiga. I came of age with a Commodore 64 per se. I first got on the internet (not just Quantumlink and the like...real internet via Delphi.) But the best memory was running a BBS. Ran a BBS for many years and eventually grew to having 4 1541's for storage and eventually a "1 meg" drive. Ran Ivory Joe mainly but also tried CNET a time or two. Eventually sold that setup for an Amiga 500 (and eventually 2000) and held on to that until the early 2000s but by 94, I also had a "PC."

@JaredBusch said:

I have no idea what you are doing without seeing the entire section. try this. This will replace PHONE1 with the first 10 digits of PHONE1. But since this is only a single subrouting, I have no idea what is really going on here.

Private Sub PHONE1_Validate(results As EntityValidationResultsBuilder)
    ' results.AddPropertyError("<Error-Message>")
    PHONE1 = PHONE1.Substring(0, 10)

End Sub

Neither do I...LOL. I do appreciate the help so far.

@JaredBusch said:

@JaredBusch said:

Wait wait wait.. you are using a case statement? where is the rest of this statement...

This is what a select case statement is for in VB

Private Sub PHONE1_Validate(results As EntityValidationResultsBuilder)
    ' results.AddPropertyError("<Error-Message>")
    Dim PHONE1 As String = "12345678901234"
    Select Case Mid(PHONE1, 0, 10)
        Case "1234567890"
            'do something here.
        Case Else
            'do something else.
    End Select
End Sub

@JaredBusch said:

This would be the VB to split out the string.

    Dim telephone As String = PHONE1.Substring(0, 10)
    Dim extension As String = PHONE1.Substring(10, 4)

OK...I made the variable declarations and forgive me if I don't know how to write code but I've tried various combinations of code and it accepts it but still shows 14 digits in the PHONE1 field...last case I used was:

Public Class RM00101Item

    Dim telephone As String = PHONE1.Substring(0, 10)
    Dim extension As String = PHONE1.Substring(10, 4)

    Private Sub PHONE1_Validate(results As EntityValidationResultsBuilder)
        ' results.AddPropertyError("<Error-Message>")
        Select Case Mid(PHONE1, 0, 10)
            Case Is = PHONE1
                telephone.Equals(True)
        End Select

    End Sub
End Class

I am sure that is not the correct method but unsure what to do on this LightSwitch / VB language...

Let me give some of this a try...will report back results...

@NetworkNerd said:

How about something like select left(phone1,10), left(phone2,10),... from table....?

That should pick off only the 10 leftmost characters and trim off the last 4.

I've tried that and perhaps it is just trying to find the exact place for this command. In LightSwitch, you have an option under properties for the PHONE1, PHONE2, etc. for CUSTOM VALIDATION and it brings up a code window. In this window, I had added a similar command as you suggested:

Namespace LightSwitchApplication

Public Class RM00101Item

    Private Sub PHONE1_Validate(results As EntityValidationResultsBuilder)
        ' results.AddPropertyError("<Error-Message>")
        Select Left(PHONE1, 10)
        End Select
    End Sub
End Class

End Namespace

It is correct syntax for LightSwitch (Visual Basic), but it still doesn't shave off the last 4 digits.

I know LightSwitch isn't popular but it is fairly easy for me to whip up easy applications. Just need to get it just right to work.

I've got a SQL table I've imported into Visual Studio LightSwitch 2013 that came from Microsoft Dynamics Great Plains 2010. Everything looks great except for Phone Numbers...they are all in a 14 digit format (last for digits for extension number) and LightSwitch cannot parse this with its own Phone Number data type.

I was wondering if there was a SQL command where I can run against the phone number columns (Phone1, Phone2, Phone3 and Fax) that would remove the last for digits. Currently they show as 00000000000000 . I am thinking if I can remove those last 4, LightSwitch will parse correctly.

Thanks...
Brian

I learned the basics here:

http://channel9.msdn.com/Series/HTML5-CSS3-Fundamentals-Development-for-Absolute-Beginners

I've had the original Surface RT, Pro, Pro 2 and now I've pre-ordered the 3 (I sold or passed down the others). I am pretty excited about this one. To me, it made my Pro 2 seem clunky and outdated immediately. Even with the improvements, I still may feel like I may need a tablet for this or a laptop for that. But for the most part, I think the Surface Pro line has been excellent.

@Dashrender said:

How many DCs and DNS servers do you have now?

Did you remove WINS from the DHCP options?

Still have the new Server 2012 and the soon to be demoted 2003. I've not removed WINS yet due to the need to check the legacy systems in our machine shop.

Good Morning...it seems to be stable now. Here's what I did but not sure what fixed it.

The reverse lookup zone showed an UNKNOWN IP for the new DC/DNS server. Added it.
Rebooted the file server (which was the only one having DNS name resolution problems).

That's really it...I spent most of the time giving users workarounds.

The NEW DNS server shows no replication issues at all. Looks healthy.

Thanks for the help on this. I appreciate the positive candor in the midst of gaps in my DNS knowledge...

@scottalanmiller said:

@garak0410 said:

@Dashrender said:

Assuming you didn't install WINS on your new AD server you should remove the WINS information from all clients and from the DHCP server so it's not handing out that information.
This will also cause issues in some cases.

Let me take a look at this.

Now, I KNOW I checked this but I guess I overlooked it and I know it wouldn't just go away. There was no reverse lookup for the file server (services01 is its physical name). I just added it.

Good to have but should not matter.

k...this morning has been rather quiet SO FAR. Only one user had problems.

@Dashrender said:

Assuming you didn't install WINS on your new AD server you should remove the WINS information from all clients and from the DHCP server so it's not handing out that information.
This will also cause issues in some cases.

Let me take a look at this.

Now, I KNOW I checked this but I guess I overlooked it and I know it wouldn't just go away. There was no reverse lookup for the file server (services01 is its physical name). I just added it.

@scottalanmiller said:

See the search name in the working one? That is missing in the not working one I think.

I see it in both.

Is there any clue as to why this is ONLY name resolution problems to the fileserver and nothing else?

This is from a PC that never lost it's naming to the FILESERVER:

Windows IP Configuration

Host Name . . . . . . . . . . . . : accounting01
Primary Dns Suffix . . . . . . . : domainname.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domainname.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : pinnstr.local
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-30-67-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d80:7b35:xx(Preferred)
IPv4 Address. . . . . . . . . . . : xx.xx.xx.xx(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, May 21, 2014 8:00:34 AM
Lease Expires . . . . . . . . . . : Thursday, May 29, 2014 8:00:01 AM
Default Gateway . . . . . . . . . : 10.xx.xx.xx (our firewall)
DHCP Server . . . . . . . . . . . : 10.xx.xx.xx (old DC/DNS server)
DHCPv6 IAID . . . . . . . . . . . : 234893415
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-8D-07-0C-00-30-67-61-63-9C

DNS Servers . . . . . . . . . . . : 10.xx.xx.xx (new DC/DNS Server)
10.xx.xx.xx (old DC/DNS server)
Primary WINS Server . . . . . . . : 10.xx.xx.xx (old DC/DNS server)
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.domainname.local:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : domainname.local
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

From a PC I had problems with today (and still do):

Windows IP Configuration

Host Name . . . . . . . . . . . . : estimating02
Primary Dns Suffix . . . . . . . : domainname.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domainname.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domainname.local
Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connec
tion
Physical Address. . . . . . . . . : 00-1E-4F-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3156:295c:xx(Preferred)
IPv4 Address. . . . . . . . . . . : 10.xx.xx.xx(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, May 13, 2014 3:14:11 PM
Lease Expires . . . . . . . . . . : Thursday, May 29, 2014 9:55:01 AM
Default Gateway . . . . . . . . . : 10.xx.xx.xx (firewall)
DHCP Server . . . . . . . . . . . : 10.0.0.16 (old DC/DNS server)
DHCPv6 IAID . . . . . . . . . . . : 234888783
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-61-xx-xx-xx-xx-xx-xx-xx-xx

DNS Servers . . . . . . . . . . . : 10.xx.xx.xx(new DC/DNS server)
Primary WINS Server . . . . . . . : 10.xx.xx.xx (old DC/DNS server)
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.domainname.local:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : domainname.local
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

I noticed on the new DC/DNS server, under the reverse lookup ZONE properties, under NAME SERVERS, the new DC/DNS server shows UNKNOWN...OK to update it?

@scottalanmiller said:

@garak0410 said:

@scottalanmiller said:

So on a user's system when it is failing, what is an nslookup of the A and CNAMEs returning?

What is the preferred syntax to check the A and CNAME with NSLOOKUP? Thanks....

Just....

nslookup aname
nslookup CNAME

Where aname and CNAME are the host names. There is no further syntax.

On PC's that had no problem or had a problem, they either NSLOOKUP ANAME or CNAME to the old or new DNS server...and they all end with can't find cname: Non-existent domain (same with aname)

@garak0410 said:

@Dashrender said:

Even more simple than an NSLookup... what does IPconifg /all return on a computer that is having problems?

Even though DHCP is off on old and new DC/DNS server, it does contain info there...

One of the PC's that cannot resolve the name to the FILESERVER shows:

DHCP Server: Old DC
DNS Server: New DC
Primary WINS Server: Old PC

On my PC (Which is on Windows 8.1), doesn't return DHCP or WINS server info...and I've never had the DNS problem.

Keep in mind, this PC and resolve all other server and PC names EXCEPT the FILESERVER.

Also, on a PC that is working and where I manually set the preferred DNS to the new DC and made the alternate the old DC, he also shows DHCP from the OLD DC.

I've really had no real solutions...just Band-Aids to get people up.

@Dashrender said:

Even more simple than an NSLookup... what does IPconifg /all return on a computer that is having problems?

Even though DHCP is off on old and new DC/DNS server, it does contain info there...

One of the PC's that cannot resolve the name to the FILESERVER shows:

DHCP Server: Old DC
DNS Server: New DC
Primary WINS Server: Old PC

On my PC (Which is on Windows 8.1), doesn't return DHCP or WINS server info...and I've never had the DNS problem.

Keep in mind, this PC and resolve all other server and PC names EXCEPT the FILESERVER.