Re: PING

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Note - the nonworking PC can ping the IP and can ping the hostname. It ONLY
cannot ping the companyweb.

Thanks for your continued help.

-- RR

"SuperGumby [SBS MVP]" wrote:

> hmmm, odd that you don't get replies. Can you suggest any reason why a
> workstation on your domain cannot ping the server it is connected to?
>
> Z:\>ping companyweb
>
> Pinging sbs.lc.lan [192.168.250.2] with 32 bytes of data:
>
> Reply from 192.168.250.2: bytes=32 time<1ms TTL=128
> Reply from 192.168.250.2: bytes=32 time<1ms TTL=128
> Reply from 192.168.250.2: bytes=32 time<1ms TTL=128
> Reply from 192.168.250.2: bytes=32 time<1ms TTL=128
>
> Ping statistics for 192.168.250.2:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> The 'additional info' part is behaving as expected, except I would expect
> the certificate to be issued by 'publishing.WebCulture.local, companyweb,
> blackvelvet, blackvelvet.WebCulture.local'. Been doing any customisation of
> certificate like info? (which doesn't explain much really)
>
> Glad to see you've found how to reply to a thread, makes it a little easier
> to follow the conversation.
>
> "Rip Rowan" <RipRowan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:758DFE68-1E92-4590-944B-661C26B755C7@xxxxxxxxxxxxxxxx
> > "SuperGumby [SBS MVP]" wrote:
> >
> >> What happens when you 'ping companyweb' from a ws? Does it resolve to
> >> 192.168.1.3? Do you get replies?
> >
> > It resolves to 192.168.1.3, but no replies.
> >
> >> Have you completed the 'to-do' list in the SBS console?
> >
> > Yes.
> >
> > Additional Info - I can access companyweb through https in this manner
> >
> > https://192.168.1.3:444
> >
> > When I do so however I get a warning telling me that "the name on the
> > security certificate is invalid or does not match the name of the site"
> >
> > When I click Details I can see that this certificate is issued to
> > blackvelvet.webculture.dynalias.net. This is a dynamic DNS I will use to
> > access the SBS instance.
> >
> > I am assuming that I am getting this error because I am accessing the
> > server
> > by IP instead of "*.webculture.dynalias.net"
> >
> > ALSO when I accept the warning, I then get prompted for a password (!!)
> > shouldn't A/D already have me authenticated? Could this be the problem
> > somehow?
> >
> > Thanks for help!
>
>
>
.



Relevant Pages

  • Re: Cant access companyweb from client computer
    ... odd that you don't get replies. ... Ping statistics for 192.168.250.2: ... the certificate to be issued by 'publishing.WebCulture.local, companyweb, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Company WEB and remote access
    ... see if you can "ping ... again before you connect to the companyweb. ... >as for your internal client what type of client is it. ... >> server but cannot from a remote internet connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Accessing Companyweb via VPN
    ... ping ip_address_of_server ... Would you consider access to companyweb via RWW instead of VPN? ... Les Connor [SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • Companyweb "page can not be displayed"
    ... I can access the server default site and companyweb just fine from an XPPro ... Win98, one running XPHome, which can see the server default site, can ping ... for DNS from the server as the only DNS setting. ...
    (microsoft.public.windows.server.sbs)